Preface
This chapter describes the basic introduction of related modes in software testing
1. Software development model
1. Waterfall model
- It is a kind of linear model. It occupies an important position in all models and is a foundation of all other models.
- Each stage is executed once, and software development is carried out in a linear sequence.
- Entry point for testing: after the testing phase is in the software implementation, enough time must be left for testing activities after the code is completed , otherwise it will lead to insufficient testing and many problems will not be exposed until the later stage of the project. (For example, the development cycle of a project is 3 months, the first two and a half months are used for development, and only half a month is used for testing. The testing time is very tight and it will be handed over to development for modification and regression and defect testing, which will obviously lead to insufficient testing)
1) Advantages:
- The various stages of development are relatively clear.
- Emphasize early planning and needs investigation.
- Suitable for product development with stable demand.
2) Disadvantages:
- Relying on early needs surveys and not adapting to changes in needs.
- A single process is irreversible.
- Risks are often delayed until later, and the opportunity for early correction is lost.
3) Improvement:
- Following the linear thinking of the waterfall model, each stage is refined, and iterative thinking is incorporated between certain important stages.
2. Rapid prototype model
- Simply put: it is to create a basic model framework by yourself, the main functions are first laid out, and then users can evaluate, change according to user needs, add additional requirements, and gradually improve
1) Advantages: Suitable for software with uncertain requirements.
2) Disadvantages: Not suitable for developing large-scale systems.
3. Spiral model
- making plans
- Risk Analysis
- Implementation development
- Customer evaluation
2. Software testing model
1. V model (important)
1) The overall process:
- Requirement Analysis-"Outline Design-"Detailed Design-"Coding-"Unit Test-"Integration Test-"System Test-"Acceptance Test
2) Basic introduction
- 1. Unit testing: also known as module testing, testing for a single program module
- 2. Integration test: Also called assembly test, all modules are tested on the basis of unit test.
- 3. System test: The whole software is tested as a whole, including function, performance, compatibility
- 4. Acceptance test:
(1) The internal communication version of the internal beta version (alpha) may have many bugs, and users are not recommended to install it.
(2) The beta version is open to all users, and the details will be modified through user feedback.
(3) The candidate version (gamma) is almost the same as the official software.
3) Advantages and disadvantages:
-
Advantages:
1. Contains low-level testing (unit testing) and high-level testing (system testing);
2. Clearly identify the various stages of development and testing;
3. Gradually refine from top to bottom, each stage has a clear division of labor , which is convenient Control of the overall project. -
Disadvantages:
1. The top-down sequence leads to errors. After the test work is coded, errors cannot be modified in time ;
2. In actual work, requirements often change, resulting in v model steps, repeated execution, and a large amount of rework , Low flexibility . -
Improvement: each step can be a small iterative work
2.W model
- Definition: develop a v; test a model combined by v (w model is also called double v model)
1) Advantages:
- Development and testing are accompanied by the entire development cycle, and requirements and designs must also be tested;
- Earlier intervention testing can find initial defects and low repair costs;
- Work in stages to facilitate overall project management.
2) Disadvantages:
- The relationship between development and testing is still linear, and requirement changes and adjustments are still inconvenient;
- If there is no documentation, the w model cannot be executed at all;
- Higher technical requirements for project team members;
3) Summary:
- The v model is suitable for small and medium-sized enterprises, the w model is suitable for medium and large enterprises (because of the high personnel requirements), and the h model has very high personnel requirements and is rarely used by companies.
3. H model (generally not used, the requirements for the entire project team are very high)
It completely separates the test activities, forming a completely independent process, and clearly shows the test preparation and test execution.
