I was given this webpage to read, by my QA Manager: tips for quality testing. It really tells you what testers need to do to be a good tester.
A few pointers I have learnt from reading such material, is:
- Find quality bugs and not quantity of bugs
- Prepare your documents early, as in create your documents / test scripts early before you start actual testing (I'm guilty here again).
I was also given this webpage to have a read through : Things that all testers should stop doing. There is a point in this article (that I mentioned above):
Power is not in numbers : It’s never the amount of defects you should be headed to, but their value. If you have located 10, 30, 50, no matter, defects during the session priorities them first and then only decide what to do with them. Some may require rapid attention from developers, others can wait. No actual matter what the case, you should be responsible for highlighting places that require immediate fixes and if you will report a whole bunch of multi-level bugs, you will only achieve chaos. Developers are like children; don’t make things even more complicated for them.