“All I Really Need to Know I Learned in Kindergarten.” Use your rules of childhood into guidelines for living life as a tester.
If you are a experienced tester on any project then help the new developers on your project. Some testers have habit to keep the known bugs hidden till they get implement in code and then they write a big defect report on that. Don’t try to only pump your bug count, share everything with developers.
Let the developers know any bug you found in design phase. Do not log the bug repeatedly with small variations just to pump the bug count. Build trust in developer and tester relation.
Don’t hit people:
As a tester you should not always blame developers for the bugs. Concentrate on bug, not always on pointing that bug in front of all people. Hit the bug and its cause not the developer!
Put things back where you found them:
You probably use a test lab. It’s probably a common resource used by other testers. When you are finished, put things back–reconfigure the hardware, restore the software, reload the test data, set up the accounts, and reset the parameters.
Clean up your own mess:
When you finish doing any test scenario then reconfigure that machine to its original configuration. The same case applies for bug report. Write a clean effective bug report. Let the developer find it easy to repro and fix it.
Don’t take things that aren’t yours:
Do not take others credit. If you have referred any others work, immediately give credit to that person. Do not get frustrated if you not found any bug that later has been reported by client. Do work hard, use your skill.
Say you’re sorry when you hurt someone:
As testers, we’re in the error-discovery business. Our job is to find other people’s mistakes. When we find them, we report them publicly. We know to always focus our reports on the errors, not the person who made the errors. But still, sometimes egos are bruised; sometimes feelings are hurt.
Say “I’m sorry.” It is one of the most powerful, healing phrases in the human language.
Wash your hands before you eat:
In other words–start clean. Once the system fails, it may not be in a stable state to look for more defects. Reboot or reload often.
Remember to flush:
Like the toilets flush all the software’s at some point. While doing performance testing remember to flush the system cache.
Live a balanced life:
There are things in life in addition to testing–friends, family, travel, love, food, rest, health, fitness, art, recreation, good deeds, spirituality, learning, play, and, of course, introspection.
It is difficult, especially in the early years of our careers, to put work aside and focus our attention on other things.
But, as the great philosopher Ferris Bueller once said, “Life moves pretty fast. If you don’t stop and look around once in a while, you could miss it.”
From a testing viewpoint, create diversified test teams and develop diversified test strategies.
Learn some, think some, draw some, paint, sing, dance, play, and work every day:
This one is more difficult to apply. How about “Learn some, think some, model some, explore some, document some, communicate, and test every day”?
Take a nap everyday:
We need time to think, get refresh or to regenerate our energy.
Some times its important to take one step back in order to get fresh insight and to find different working approach.
When you go out in the world, watch for traffic, hold hands, and stick together:
Always work in teams, team score are always better and powerful than individuals.
Be aware of wonder:
Be aware of wonder as a tester: the wonder that they made so many stupid mistakes; the wonder that so much actually does work; the wonder that your organization is still in business; the wonder of your own talent as you discovered an amazingly convoluted bug in the code; and the wonder that you have so much fun and get paid for it.
Now its time to take nap Happy Testing!