1) Programmers should not test their own code.
2) Go beyond requirement testing.
3) When Regression testing started, use the previous bug graph/Defect tracking tool.
4) Analyze code changes are done properly for testing purpose. If not don't accept the build.
5) Keep developers away from test environment but never hurt them.
6) Testers need to be right from software requirement and design phase.
7) Share your best testing practices/experience with your testing friends.
8) Think of positives and negatives while going into an application.[Technically and Non-technically]
9) Before testing, Learn to analyze the whats your plan.
10) Test cases needs to be available to developers prior to coding, so that they can't blame you.
11) Write clear, descriptive, unambiguous bug report.
12) Increase your conversation with developers so that you might get a new direction to test the application/modules.
13) Understand how programmers think and do the other way.
14) Ask them questions to client/developers/QA managers. It might be silly but don't hesitate. Some questions can be a turning point of your project/product.
15) Avoid keep all your communication in the mode of verbal.
16) Think like an end user. Listen to end user more and developers less.
17) Learn to say NO when quality is insufficient. Deliver with quality.
18) Increase the learning curve in automated test tool programming.
19) Know your application and domain.
20) Don't be diplomatic.
No comments:
Post a Comment