Software Testing and Quality assurance:
1. Software Testing:
A. test: The process of executing a program in order to discover errors in a program during testing.
B. Test cases: test data and expected output results are called test cases.
C. Test method: White/black box
D.
| Category |
Stage |
Executive person |
Case |
Way |
| Unit Test |
Coding phase |
Programmers |
Programmers |
White box |
| Group testing |
Detailed design |
Programmer's Team |
Programmer, Simulation/user Data |
White/black box |
| System Testing |
Architecture/Design |
Specialized Testers |
Analog data |
Black box |
| Validation/Acceptance Testing |
Demand analysis |
Third party testing Company (user) |
(analog) User data |
Black box |
| Regression test |
(development) Operational maintenance |
Testing staff |
Programmers |
White/black box |
2. Quality Assurance:
A. Software quality = Program Quality + Software engineering quality
B. Software = program + Engineering
D. Quality of software: The quality of software is reflected in the quality of the external functions of the software (measuring the function of the software, the basic judgment can be used to "yes | no" to determine)
E.cmmi Software Competency Maturity Model (P289)
3. The relationship between software testing and software quality Assurance
A. The same point: all of the two different levels of software quality engineering work.
B. Different points: Software testing: <1>, to meet the quality requirements of the product to take the operation of technology and activities;
<2>, The aim is to prevent unqualified products from being put in, transferred and shipped to the factory to ensure that the product meets the quality requirements and only qualified goods can be delivered to customers.
Software Quality assurance: <1> to meet customer requirements to provide trust, even if the customer is confident that the products you provide to meet his requirements;
<2>, the aim is not to ensure the quality of products, to ensure product quality is the task of software testing;
14th Week Summary