[test development] software testing - Basics

The life cycle of software testing （ Software testing process ）

review ： The life cycle of software development ：

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

Software testing process ：

Demand analysis — test plan — Test design / Test Development — The test execution — Test evaluation

The tasks of each stage ：

1. Demand analysis ： Verify the correctness of the requirements , rationality ; Refine requirements , Find the test item , Write test cases
2. test plan ： Determine the number of test personnel , Test environment , Test time , Test equipment
3. Test design / Test Development ： According to the demand , Write test cases
4. The test execution ： Development has been completed , Execute test case , Verification function ; If there is BUG, Submit BUG, verification BUG
5. Test evaluation ： How many test cases have been written , How many , Number of test cases remaining ,BUG Quantity and solution BUG Number , The legacy of the BUG And Solutions , Test scope and test function

How to describe a BUG

It includes the following parts ：

1. Test version number （ Code version information ）： The tester needs to make changes BUG Developers of know the version with problems , Help developers get the corresponding version of code to reproduce BUG
2. Test environment ： If it is web System , Then the hardware equipment information description includes computer brand and model , The software device information description includes the operating system , browser （ Which browser , What is the version number ） etc. ; If it is APP Words , The software equipment information includes the version number of the system （ Which system is it , Android /IOS/windows/ Hongmeng ）, Hardware equipment information includes mobile phone brand （ What series ）, Computer brand
3. Test data ： It can reproduce the problem more quickly
4. testing procedure
5. Test actual results
6. Test expected results
7. The attachment , Error log , Error screenshots and so on

BUG The level of

ps： Every company is different , This is just a common situation

1. collapse ： The system doesn't work , There's a breakdown , Operation deadlock , Dead cycle , Black screen , Hinder the work of testers
   What should we do if there is a crash online ？ How to remedy ？️ Go back to the last stable version
2. serious ： The system can run , But it's not stable , Continued operation will cause serious losses , Important functions are not realized , Or the functions and requirements do not meet , User data storage error in database , Threaten the safety of users （ Information , property ）
3. commonly ： The secondary function is not realized , Or something wrong , The system can run stably
4. Suggest ： All functions are realized , But it will affect the user experience , Such as ： Typesetting , The color is not in line with public aesthetics , The message does not wrap , Or wrap in advance

BUG Life cycle of

because BUG What to do with conflicts with developers ？

1. Check , see BUG Is the description clear
2. Persuade developers to modify from the perspective of users
3. BUG The grading should be justified （ According to the company's specifications ）
4. As a tester, we should constantly improve our business level and technical level , Not only can we find BUG, And be able to locate , Can also propose solutions
5. Don't quarrel , Talk to the product manager about , Tripartite meetings ： Testers , Developer , The product manager will discuss this BUG The ultimate solution