"Correct definitions can prevent or end the debate ." -Nathanael Emmons
Under the compelling "test" title, there are often a lot of jobs that require different skills. Such a general approach affects planning, estimation, assignment of work, and may even cause damage to the entire project.
Common Errors:
1. It is considered that a time plan can be made for 'location error '.
2. The time loss caused by task switching is not considered. -- If the number of tasks to be switched reaches 5, no work may be completed.
3. Use testing as a low-priority task that can be interrupted for any reason. -- Reliable testing requires concentrated efforts
4. The tester is required to identify each fault. -- This work is basically the responsibility of developers.
5. The tester is required to locate each fault-this is entirely the work of the developer. Tester does not have the corresponding skills, although sometimes it provides some helpful clues
6. Modify without retesting
7. Ignore the cross-connection relationship-test and programming are connected together
8. Insufficient attention to testability:Designed and built for testingCodeThis significantly reduces the time and effort required for testing in all aspects.
9. insist that all defects should be 'reproducible'
10. obfuscated tests and "Creating and executing test cases"
11. make major adjustments to the company's development process