But not all of us get to develop the main source and even be a part of that development cycle in industry. So, should you be unhappy on the testing role offered? Absolutely not!
Testing is a very responsible job. No product goes into the market unless it is thoroughly tested and gets the approval of the tester that it is good to go. This role is not easy and can be very interesting. As a tester, you know the behaviour of the software more than the developer himself. You are the first client. Testing the real time scenarios, you are a bridge between the market and the development. Trust me, it is very exciting.
So, how should you go about testing?
Here are some tips on better testing:
1. Understand what is to be tested.
Know the software thoroughly. Go through the document given by the developer.
2. Ask for more.
Discuss with developer about the software's behaviour, its implementation etc. The more you involve in it, the more bugs you can find.
3. Plan your tests.
Write down the plan of the tests. This should list all the tests. Be sure to do negative testing. Often, software works in normal cases. But goes for a toss in negative conditions. Include real time scenarios, customer situations. Think like a customer.
4. Implement your tests.
Choose an efficient testing tool or language. Plan your implementation well. Remember, tests should be as efficient as the main code you are testing. This is the most interesting part. Here, you get to do automation around the software, learn new products. Can be innovative as well!!
5. Identify the bugs.
Writing tests is not all. You need to understand the erring cases, identify the defects. Get them fixed. Critical defects are highly appreciated, because you are catching them before the software goes in market. This actually saves alot!
6. Get the bugs fixed.
Let the developer fix the defect. Re-test the fixed code. Feel free to say NO, if you are not happy.
Testing is really a responsible job role. Be proud to say you assure the quality of the software to be delivered!