[Software Testing Learning] - Basic Understanding of Software Testing (1)
Article directory
-
- [Software Testing Learning] - Basic Understanding of Software Testing (1)
- 1. What is software testing
- Second, the purpose of software testing
- 3. Principles of testing
- 4. Test standard
- Five, the basic requirements of the test
- Six, the origin of the bug
- Seven, the test process
- 8. Development mode
- Nine, the relationship between testing and development
1. What is software testing
To sum it up:
- The process of operating or testing a system by manual or automated means.
- The purpose is to check whether it meets the specified requirements.
- Figure out the difference between expected and actual results .
Second, the purpose of software testing
The purpose of software testing: to find potential errors and defects in the software with the minimum manpower, material resources and time
3. Principles of testing
4. Test standard
As a software test engineer, the first knowledge that requires in-depth understanding is the software quality model. For testing, the job is not just to mention defects, but also to evaluate product quality. How to evaluate product quality, whether the evaluation result is objective, whether there are standards or dimensions that can be analyzed.
Before evaluating the quality of the product, we need to figure out what the product quality is? According to the definition of IEEE24765-2010, product quality is only "the inherent characteristics of the product to meet the expressed and implied requirements under specific conditions of use", in short, quality is to meet the requirements. Carrying out software quality assessment, the main content of the assessment is actually whether the product meets the needs of users.
Products that meet user needs not only meet the functions that are clearly mentioned in the product requirements, but also meet invisible needs such as industry norms, conventional requirements, or user habits. Due to different industry backgrounds, different personal knowledge reserves, and user needs may be deformed and distorted during the transmission process, we need to use the software quality model for system analysis to identify these hidden needs, prevent defects, and improve products. quality.
ISO/IEC 25010
Compared with 9126, 25010 expands the quality model from the original 6 attributes to 8 attributes. The newly added content is security and compatibility. In addition, the functionality, ease of use and maintainability have been modified. Specifically The content is as follows.
Five, the basic requirements of the test
Six, the origin of the bug
Seven, the test process
8. Development mode
waterfall model
Incremental model
Rapid model
Other development models
spiral model