Tuesday, January 8, 2008

Automate testing

If your tester have to do the same movements from day to day to check the main functionality, that is especially actual on the project release stages, than she will have not much time to test the application "intellectually". Accordingly - the quality come down. And customer's satisfaction of the project results comes down too.

I see the following outlet from this situation (this is not complete solution - but required part of problem decision process):
  1. Allocate  dedicated automation functional testing team (quite possible, it's necessary to partly put this team work cost into the project price). Why separate team? To rear an automation tester from every functional tester is expensive, long and ineffective (and sometimes is almost impossible).
  2. Tester should write a testing plan (e.g., Minimal acceptance test plan) for the automation testers.
  3. Tester should know how to execute automated tests and to analyze their results.
Thanks to this we have:
  1. Well-qualified team of automation testers, services of which could be sold and which perform automation tasks quick and with high quality.
  2. The minimal set of regressive tests, that could be run in a nightly manner, for example, for every build. It should decrease the number of overlooked errors.
  3. Increase of time, that tester spends testing the complex and/or new functionality.
  4. Quality growth
It remains just to convince boss of the truth of my words :)

No comments: