Don’t be afraid to ask questions
As you all must know Testing is about questioning. The more you question the more you will know about the project/product under testing. Question everybody – product vendors, developers, other testers in the team, team leads, managers, your client and anybody who has the interest in the project/product under test. Don’t bother what people think, just ask whenever you have some relevant query.
Face the challenges
Always be ready to face any challenge. If you are asked to test which you are not familiar with, grab the offer with both hands. This will give you an opportunity to learn not only about that product, but many related things which you didn’t know earlier. Just say to yourself – “I can do it”! It is possible that you won’t do so well the first time, but next time you will do better.
Mentor the mentee
“The Brain Power is greater than the Brawn Power”
knowledge is the only thing that the more you spend the more you will get. If you get the chance, share your knowledge with new aspirant testers. This will help them to do well in Software Testing and you will also learn from them. You can get knowledge and ideas which you might not have or which you never thought of. If possible, share your knowledge, ideas, views and experience on different discussion forums.
Communication leads to Test Coverage, not just Requirements
We often ignore Communication. Communication is a tool, an important tool for your test coverage. Oral or Written or Chat Communication is medium to record the requirements for test coverage.
Not all Requirements could come from Requirement docs. The medium of communication is not important here. What's important is how well we gather the "Information" and document it and then share it as just "Minutes of Meeting" or a Word doc or a Scenario/s or even a test case/s.
There is no right or wrong way of understanding requirements as long as it suffices the Business Needs of the Customer.
Last but not Least, Love your job
This is not applied to Testing particularly; this is applied to any job and every job. You must have passion for what you are doing. If you have passion for your job, any organization will pick you and you’ll get immense pleasure from what you are doing.
As you all must know Testing is about questioning. The more you question the more you will know about the project/product under testing. Question everybody – product vendors, developers, other testers in the team, team leads, managers, your client and anybody who has the interest in the project/product under test. Don’t bother what people think, just ask whenever you have some relevant query.
Face the challenges
Always be ready to face any challenge. If you are asked to test which you are not familiar with, grab the offer with both hands. This will give you an opportunity to learn not only about that product, but many related things which you didn’t know earlier. Just say to yourself – “I can do it”! It is possible that you won’t do so well the first time, but next time you will do better.
Mentor the mentee
“The Brain Power is greater than the Brawn Power”
knowledge is the only thing that the more you spend the more you will get. If you get the chance, share your knowledge with new aspirant testers. This will help them to do well in Software Testing and you will also learn from them. You can get knowledge and ideas which you might not have or which you never thought of. If possible, share your knowledge, ideas, views and experience on different discussion forums.
Communication leads to Test Coverage, not just Requirements
We often ignore Communication. Communication is a tool, an important tool for your test coverage. Oral or Written or Chat Communication is medium to record the requirements for test coverage.
Not all Requirements could come from Requirement docs. The medium of communication is not important here. What's important is how well we gather the "Information" and document it and then share it as just "Minutes of Meeting" or a Word doc or a Scenario/s or even a test case/s.
There is no right or wrong way of understanding requirements as long as it suffices the Business Needs of the Customer.
Last but not Least, Love your job
This is not applied to Testing particularly; this is applied to any job and every job. You must have passion for what you are doing. If you have passion for your job, any organization will pick you and you’ll get immense pleasure from what you are doing.
No comments:
Post a Comment