| || |
Automation and small team size.
I am looking to find and learn from small teams as to how they are doing automation?(If)
We are a very small team,by small i mean Myself(QA engineer) and my manager. We purchased QTP about a year back and i am quite proficient in it.I used to be a programmer and my programming skills are pretty good.My skill level in vbs is intermediate. We are just about to do a complete re-write of our webApp to a RIA(flex) and i am pretty comfartable so far working with QTP and flexApps.I started to read about automation framework and i was boggled by the sheer amount of work and time involved. I am not just the automation engineer here so i have other responsibilites including writing test cases, executing tests(manual and automated)etc.. We have 6 programmers ... so our programmer to tester ratio seems fine doesnt it.
Looking for suggestions, help and opinion.
Re: Automation and small team size.
What a nice ratio, 6 to 1--you are a lucky dog!
As for the "right" framework for the new project:
1. Decide if you are going to use traditional Object Repository technology or DP for object definitions. This has an impact on almost anything else you then develop.
2. If you are using QTP 8.2 move to 9.2 (which is stable) or even 9.5 (stability is currently unknown at this point in time).
3. Given that you are the only automation engineer--and then only part time--I would concentrate on developing a new set of lib functions to help <u>you</u> be more productive. I am sure you have some already, but the 2nd time around we would all like to have done things differently after our virgin learning curve. I would also suggest tersely documenting these as you development them--so that when you eventually add another automation engineer--or get some temp help from the developers--this can be studied by the new person.
4. Then craft a QTP test script template that scaffolds a generic test script using "well formed" sections with a set of comments above each section about what should be placed in that section. If you are going to use "well known" shared libraries add them to that template's Test Settings Resource tab. Do the same for the Associated OR(s), if you use them.
5. Write a 3 to 5 page terse overview about how all the above flows and works together.
At that point I think you will have framework appropriate to you testing environment.