Five Lessons Learnt from my last Testing project
1. Every project teaches you something new if you are ready to learn.
I tested a web based application for the first time. Introduced to terms like IISRESET, HOSTS, PROXY SERVER, RAD GRID, AJAX, HTTPS, DOMAIN NAME, DATABASE SERVER.
2. A tester's role is to meet the mission.
I found 73 bugs in 6 hours and had to close 69 bugs because they were not at all important from the customer's perspective.
Previous Project: Found 710 issues and 685 were fixed. Everyone appreciated me.
This project: Found 73 issues and 4 were fixed. Everyone asked me to concentrate on features which the customer would use.
3. Test on the expected environment.
Tested for two weeks on an environment which was not the environment at the customer end. Now I feel, why did we waste those two weeks?
4. Test the environment first.
Believed a technical person for setting up the environment and the environment was wrong. First build to customer and it failed miserably. Tested the environment and found that a simple mistake meant that we tested on the wrong environment for two months.
5. Work as one team towards one goal.
It is good to interact with programmers, product managers, tech support, sales manager, QA head, Development Head. Everyone has something new(read different) to contribute.
WOW, I'm very happy that after three years of testing in office, this is my first product release to market.
I'd say worth the wait for three years.
So, when's the next release BOSS? I'm waiting :)
Friday, October 16, 2009
Three Years: Worth the wait?
Subscribe to:
Post Comments (Atom)
4 comments:
Congrats my friend!
Previous Project: Found 710 issues and 685 were fixed. Everyone appreciated me. This project: Found 73 issues and 4 were fixed. Everyone asked me to concentrate on features which the customer would use.
Maybe that's also an indication of the need of better bug advocacy skills. Plus the numbers don't tell the story.
How about a check on over confidence as well?
Hi Ajay,
Congrats on completing 3 years in testing.
I have been going through all these during my 4 years stint in this field. This seems to be a common experience all the testers have had, that you find a lot of bugs which deviate from the requirements.
There have been instances where during your initial release you report an bug which you have to close because it doesn't impact the system much. But then in the next release some mutation happens to the bug and it becomes a huge bug and you are screwed up as a result. I am fighting hard to find a breakthrough to this situation.
Welcome to Web App Testing! Better late than never.
A bug is a bug is a bug irrespective of its importance. If not today it will be important tomorrow.
Important for a tester "DO NOT TRUST" anyone or anything unless you are doubly sure.
Enjoy and Happy Testing.
Post a Comment