1) I always works on Cockroach theory of testing which means if you are able to find one bug in a application at one particular functionality, try to search for many more bugs in that module itself. This is because bugs are like cockroaches who always live in a group. If you able to find one, changes are quite likely that you will be able to find many more at the same place.
2) Try to automate as much as possible. It is going to make the life miserable in the start while creating the test scripts, but you will enjoy rest of you project tenure once the automation is over.
3) Divide each and every step of a test case in a separate file, test script while doing automation. It will help you to reuse various test scripts. Try to create a tracker while starting of the automation so that you are able to track the test scripts depending upon the functionality.
4) For a large application, divide the automatic test runs in such a way that multiple machines are used so that team can get the results within a short span of time.
5) Integrate the automation test suite with Cruise Control (or any other build management system) so that automation batch will get started automatically once the build is out. [In my next blog, I will talk about the automation framework which I have build for my current project and is integrated with cruise control as well].
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment