Tester's Choice

Search This Blog

Books review

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Book review (only books that I've read) *TeStars: 5 being the highest

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Comments

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

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

Bugs - Aging reports

There are two ways I know to calculate bug aging: The time that the bug was opened until now, assuming it is still open. The time that the bug is in its current status. Both metrics are interesting and co-exist because they indicate different things. The first type is asking: are we, as an organization, keeping the bug life cycle in a reasonable time? The second is more low-level and checks the actual status where the bug is stuck. The below reports are of type 2 above, time in current status. The one below is just an aggregation of the one above it. *Status Done is not monitored. **Made with eazyBI for Jira.

Powered by Blogger

Books review

Comments

Post a Comment