Basic theoretical knowledge of software testing - concept

What is software testing

Verify whether the software functions meet the needs of users

The purpose of software testing

(1） Software testing is to detect code or business logic errors in a program
(2） Software testing is to verify that the product meets the user's requirements
(3） Software testing to improve the user experience

Software defect (Bug) The concept of

The user needs ： The specification is correct , If the procedure does not match the specification , It's a software error
The software requirements ： The program does not meet the needs of the end user

The life cycle of software development

Demand analysis - plan - Design - code - test - Operation and maintenance

Software development 5 A model

(1) Waterfall model ：

• advantage ： Emphasize the stage of development ; Emphasis on early planning and needs survey ; Emphasis on product testing
• shortcoming ： Relying on the only early needs survey , Unable to adapt to changes in demand

(2) Spiral model ：

• advantage ： Emphasize strict whole process risk management . Emphasize the quality of each development stage . Provide an opportunity to review the value of the project and continue
• shortcoming ： Introduce very strict risk identification 、 Risk analysis and risk control , This puts forward high requirements for the skill level of risk management . This requires personnel 、 Investment of capital and time

(3) Iterative model ：

• Compared with the incremental model, the iterative model has a higher ability to resist risks

(4) Incremental model ：

• Incremental development can significantly reduce project risk , Combined with software continuous construction mechanism

(5) Agile development model ：

• Agile Manifesto ： Individuals and interactions are more important than processes and tools , Available software is more important than complete documentation , Customer collaboration is more important than contract negotiation , Responding to change is more important than following a plan
• Scrum Workflow
  1. The person in charge of the product is responsible for sorting user story, To the left product backlog.
  2. Release planning meeting ：product owner Responsible for explaining user story, Estimate and rank them , The output of the release planning meeting is to work out what to complete in this iteration story list ,sprint backlog.
  3. Iteration planning meeting ： The project team is responsible for every story Perform task decomposition , The standard of decomposition is to complete the story All the tasks of , Each task has a clear person in charge , And complete the initial estimate of working hours .
  4. The daily meeting ： Every day scrum master Call a standing meeting , Team members answer what they did yesterday and what they plan to do today , What's the problem? .
  5. Demo Meeting ： At the end of the iteration , Hold a demonstration meeting , Relevant personnel are invited to attend , The team is responsible for showing the results of this iteration . During this period, everyone's feedback is recorded , from po Arrangement , To form a new story.
  6. Retrospective meeting ： The project team summarizes this iteration , Found insufficient , Make improvement plan , Continue to improve in the next iteration , Continuous improvement has been achieved
  Progressive effect .

Software testing 2 A model

V Model ：

• characteristic ： It clearly indicates that there are different types of tests in the test process , And it clearly describes the corresponding relationship between the test phase and the development process phase
• limitations : Just think of testing as a phase after coding , Testing without the requirements phase ：

W Model ：

• characteristic ： It's not just programs that are being tested , demand 、 Design and so on should also be tested , Testing and development are synchronized ; It is helpful to find out the problems as soon as possible
• limitations ： demand 、 Design 、 Activities such as coding are considered serial ; There is also a linear relationship between test and development activities , The last stage is completely over , Only then can we officially start the next stage of work . Can't support agile development model . For the current software development complex and changeable situation ,W The model does not solve the confusion of test management .

The life cycle of software testing （ technological process ）

Demand analysis - test plan - Test design - Test Development - The test execution - Test evaluation

Describe software defects (Bug) Elements

(1) The version of the problem ： Developers need to know which version of the problem is , To get the corresponding version of the code to reproduce the fault . And the version identification is also conducive to statistics and analysis of the quality of each version
(2) The environment in which the problem arises ： Environment is divided into hardware environment and software environment , If it is web project , You need to describe the browser version , Client operating system, etc , If it is app project , Need to describe the model 、 The resolution of the 、 Operating system version, etc . Detailed environment description is conducive to fault location .
(3) Operation steps : Describe the shortest steps for problem recurrence
(4) The actual result : Describe the phenomenon of error .crash You can upload it later log,UI Questions can have screenshots
(5) Expected results : Let developers guide you how to be right , In particular, we should describe the behavior of the program from the perspective of the user

The level of software defects

(1) Suggest ： Interface 、 Performance defects , Suggestion questions , It does not affect the execution of operation functions , Schemes that can optimize performance, etc .
(2) commonly ： The function is not fully realized, but it does not affect the use , There are defects in the function menu, but it will not affect the stability of the system .
(3) serious ： Loss of main functions of the system 、 Database save call error 、 Loss of user data , The first level function menu cannot be used, but it does not affect the test of other functions . The functional design is seriously inconsistent with the requirements , The module cannot start or call , Program restart 、 Automatically quit , Call conflict between associated programs , safety problem 、 Stability, etc
(4) collapse ： Problems that hinder development or testing ; Cause system crash 、 crash 、 Dead cycle , Cause database data loss , Connection error with database , Loss of primary function , Problems such as missing basic modules

The life cycle of software defects

New: Newly discovered Bug, Decide whether to assign developers to modify without review
Open： Confirmation is Bug, And think it needs to be modified , Assign to the appropriate Developer
Fixed: After the developer makes the modification, it is marked as the modification status , To be verified by the regression test of the tester
Rejected： If not Bug, Refuse to modify
Delay: If you think it doesn't need to be modified or can't be modified for the time being , Modify later
Closed： Modify the state of Bug It is verified by the regression test bin of the tester , Then close Bug
Reopen： If verified Bug There is still , You need to reopen Bug, Developers re modify