Tester's Choice

Search This Blog

Exploratory Testing: First-Time Session

on March 06, 2024

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Exploratory Testing: For those who never had done it before

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Comments

What are the biggest challenges in software testing today? We've asked chatGPT

His answer: Keeping up with new technologies and changes in the software development landscape. Ensuring comprehensive testing coverage for complex and dynamic systems. Managing and automating the testing process to increase efficiency and reduce costs. Managing and preventing bugs and defects in software. Ensuring compatibility and usability across different platforms and devices. Managing and analyzing large amounts of data generated during testing. Managing and coordinating testing across different teams and departments. Ensuring security and privacy of data during testing. Managing and preventing human errors in testing. Keeping up with changing customer and user needs and expectations. **I can think of a few more, but I agree with chatGPT. original publication: Jan 20, 2023

XRAY for Jira: Failed Tests in Test Plan - how to re-run

Let’s discuss a real-life dilemma: the situation in which you have failed tests in a Test Plan: what is the correct way to re-run them? The simple – but not the best – solution is to open the Test Executions with the failed tests and re-run the failed tests. The problem is that in real-time and especially after the version ends, we will not know what was the version quality – we will see all the tests with the status Pass. But the story could be that the version was a low-quality one, 30% of the tests failed (vs usually much less), and no one will know, no one will improve the proof. Attached is a short video with 2 simple solutions for this issue: Failed Tests in Test Plan - how to re-run

Bugs Quality Dashboard

I would like to share the bugs quality dashboard we use. The report represents some criteria we thought would give us a good understanding of the quality of bugs we open, and we measure it over time so we could improve and see progress. To be sure, reports tell only a part of the story. Bugs can be rejected for many reasons, some may not be related to the situation reported. Also, for example, the failed component indicated in the bug could be based on logical assumptions even if in the end the bug was elsewhere. So the reports are just a starting point, not the conclusion. The dashboard is in Jira, like the bugs, and the reports were done using Jira plugin eazyBI. The reports Please review each clause with the picture below. The first gauge report, Bugs Integrity Level , is an aggregation of the evaluations of most of the other reports, a general view. The one under it on the left, Dev Efficiency - Bugs per resolution with drill across , shows only closed bugs (closed on that specif

Powered by Blogger

Exploratory Testing: First-Time Session

Comments

Post a Comment