Test team architecture / test principles
Organizational structure of the test team
(1) Pyramid model is
generally divided from top to bottom: test director-A product test director-test team leader-tester, with a dedicated test team. It may also be grouped by test category, such as automated testing, performance testing, security testing, etc. This organizational structure is relatively clear;
(2) The matrix model is
generally divided by project, and a project is divided into project manager, development manager, and test manager.
To understand the organizational structure of a company's development / test team is conducive to clarifying the individual's future development direction.
Separate management, professional management, project management staff, clearly divided, but the disadvantage is that sometimes the tester will fall into not knowing which one to complete first (usually prioritize the project and then deal with professional field issues)
Software testing principles
Knowledge system required by software testers
Qualities needed by soft
testers : sense of responsibility: treat the project you test as a child, know its advantages and disadvantages, and know how to cultivate the project
Principles of software testing
1. All software testing should be traced back to user needs.
That is, we should pay attention to the requirements document and clarify the initial requirements in order to reduce the errors in the later period as much as possible;
"More than 80% of product defects are introduced during the requirements definition stage of the product development process. If the requirements are accurately verified, 80 % Rework problem, saving 45% of the total project investment cost ”
2. Start the test as soon as possible to find the problem as early as possible.
The more the problem is left behind, the greater the cost of modification;
3. The pareto rule is suitable for software testing, also known as the 28 efficiency rule , which means that a large number of problems should be discovered early;
The Pareto (Pareto) rule was proposed by the Italian economist Pareto, also known as the 28 efficiency rule.
The Pareto rule in testing is that under normal circumstances, 80% of defects can be found and avoided during the review and testing of the analysis, design, and implementation phases (that is, the initial stage) and system testing can find 80% of the remaining defects , The last 4% of the defects may only be exposed after a large range of users and long-term use.
4. Exhaustive testing is impossible, and proper risk analysis should be done;
since there are few opportunities to perform all possible tests on an application software, for most software development projects, the use of risk analysis is appropriate. This requires judgment skills, common sense, feelings and experience. If there are valid reasons, a formal method can also be used.
5. Strange insecticides.
Developers will know some routines of testers after a long time, so testers should often switch their thinking and use multiple methods to test ; this is also the reason why random testing and exploratory testing have become popular recently.
6. Two steps forward and one step back.
Defect repair will always introduce new bugs with a probability of 20% -50%.
After each repair, all previous test cases must be re-run to ensure that the system will not be destroyed in a hidden manner.
7. The principle of two minds
, carefulness, confidence, patience, teamwork and communication skills , always being skeptical and flawed.
