December 26, 2020
Often times we see a challenge where manual QA would find a bug, then come to Engineers only to find out that they can’t reproduce it anymore. We’ve seen it happen time after time after time daily.
We believe part of the problem is that there is an annoying need to keep steps to reproduce clinically perfect in terms of environment, browser version, and the steps to reproduce perfectly.
As one QA professional put it: “It takes me time to write a defect with reproducible steps and even then devs can come back and say that they can’t reproduce or don’t understand.”
This is where testRigor comes in and helps our customers to have clean referenceable steps to reproduce with the screenshots that can be easily used to create a Jira ticket. It eliminates the question of how to do it since it is very clear from the steps: