How to Prove and have Evidences to provide that all manual test scenarios has been executed?



  • Historically at our company we have taken screenshots of every step in a test script, even if no bug has been found. We are now moving from a waterfall method to iterative development cycles. Over the last 6 months, we have been trialing using rapid test design using mindmaps and not taking screenshots, and instead stating that the test cases in the mindmaps and the management spreadsheets are evidence that the test has been thought of and executed. It's our belief that taking screenshots does not prove anything and actually wastes valuable testing time. However, there is some resistance with people believing the mind map or similar processes do not give them sufficient evidence if questioned at a later date about that test. I would be interesting in getting advice or others' experiences specifically relating to the following questions. Either way, we do not plan on purchasing recording tools. Do you take screenshots to prove a script has been executed or just when a bug is found? Have you found not taking screenshots to evidence a test, has caused any confrontation or issues? Have your found any disadvantages using rapid test case design and mindmaps for test analysis? Please can you state whether you work for a transnational, national, regional, or startup company. We are small, national company and would like to hear from everyone, but need take a balanced view as to what we can achieve and not achieve.



  • Anecdote: I worked on one project for a national company. Testing was being done and overseen by one of the Big Name consultancies. Their testers were told to take screenshots for every test step. They abandoned this practice as (1) it was taking too much time and test progress was too slow and (2) I was fnding 90%of the defects on the project by doing exploratory testing.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2