Im trying to figure out how well let our testers know that any failed tests have been fixed and are ready for retesting. How about if I add a result code for this?
Yes, that’s a great idea, and easily done as ApTest Manager lets you configure your result codes. Further, if you include a link to ApTest Manager in your Problem Reports, your developers can use them to mark an issue as ready for retesting within ApTest Manager. In this model there would be a a link put into the PR in the bug tracking system to the ApTest Manager run page for the test the PR was filed for. These links can be included automatically in the information ApTest Manager submits when a bug is created. When a bug is fixed the developer would click the link to bring up the run page so they can a) rerun the test to verify the fix and b) change the test result to one indicating it is ready to be verified (and optionally add a comment about the fix). As ApTest Manager keeps a running history of every time a test is run this would record the developer who made the fix, which is a nice info for QA to have. When QA got a new drop with fixes they could ask ApTest Manager to rerun jus
Related Questions
- People with chronic pain may try very hard to figure out what’s causing their pain and they go through a lot of tests and imaging to find out the cause. What are your thoughts on that?
- Im trying to figure out how well let our testers know that any failed tests have been fixed and are ready for retesting. How about if I add a result code for this?
- What if the police officer thinks I failed to perform the field sobriety tests to their standards?
