2

We are following Agile Scrum in our project. While manual testing, we would like to maintain test execution proof which should be easy to capture and easy to maintain.

Currently, we are following the manual process of taking screenshots and using "Quick Time Player" for recording.

Can anyone suggest the better way of recording/capturing/maintaining of test execution proofs?

  • 3
    To suggest a better way we need to know what is the way you're currently using. – Alexey R. Nov 20 '17 at 10:29
  • Are you using automated testing? If yes , you may configure it to take screenshots at critical verification points. – Vishal Aggarwal Nov 20 '17 at 17:11
  • Since you have not mentioned what you are currently using, I'd suggest making use of automated Test Reports. Guess this will serve your purpose of maintaining Test Execution proof. – bane19 Nov 21 '17 at 1:53
  • Currently, we are following the manual process of taking screenshots and using "Quick Time Player" for recording. – SagarK Nov 21 '17 at 10:44
3

Automate it, run it on a build-server.

I will produce, with each release, a quick, sure, and repeatable proof that every element of the code works as it should.

http://blog.cleancoder.com/uncle-bob/2015/11/18/TheProgrammersOath.html

If for some reason you do need todo it manual have a look at Session-based test management. This seems to be Agile "compatible" and contains proof.

Still focus on automating most if not all of your test-cases. Preferable with lots of unit and integration tests.

Suggested resources:

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.