Introduction software testing tips

You must keep these common sense of software testing in mind ：

01、 software test （ The significance of software testing ）

1、 The process of finding errors in a program and executing it

2、 Check whether the product meets the needs of users

3、 Improve user experience

02、 Software testing principles （ common sense ）

1、 Early intervention （ Intervene in requirements analysis ）

2、 Trace back to user requirements （ Don't build a car behind closed doors ）

3、 Programmers should avoid checking their own programs , In addition to unit testing . Front test ＋ Negative test 28 principle ,80% Our mistakes focus on 20% In the module （ Aggregation effect ）

4、 There is a process of confirming the wrong results （ Do more tests , Record the test process , Occasional form BUG）

5、 Make a strict test plan （ Starting time 、 Responsible module …）

Complete testing is impossible , The test needs to be terminated （ There will be some reasonable BUG, Does not affect the user experience and use of , these BUG It may have to be changed in the next version ）

03、 Classification of software testing

One 、 According to the test stage ：

unit testing 、 Integration testing （ Both developers and testers can do , Interface testing is divided into integration testing ）、 The system test （ complete 、 A test of the whole , Not Android 、 Apple system ）、 The acceptance test （ Formal acceptance test 、Alpha test 、Beta Test game internal test 、 Pre release version 、 Public survey ）

notes ：Alpha test ： Early user testing , Conduct acceptance test under simulated actual operation environment （ Internal measurement ） It belongs to the development environment , Development and testing cannot be involved

Beta test ： Post user testing , In a real environment （ Public survey ）, Development and testing cannot be involved

The same thing ： Neither development nor testing can be involved

Difference ： In the early 、 later stage , Development environment and real environment

Two 、 By test technology ：

White box testing （ Code level ）、 Black box testing （ Through external operation and surface reaction ）、 Grey box testing

3、 ... and 、 According to the content of the test ：

A functional test （ Dot ）、 Interface tests （UI Interface ）、 Security testing 、 Compatibility test 、 Ease of use test （ It's easy to get started ）、 Performance testing 、 Pressure test 、 The load test 、 Recovery test （ Disaster preparedness , Self repair ）

Four 、 Other tests ：

Smoke testing （ Backbone testing before release , Before the real test ）、 regression testing （ Verify that the test repaired BUG And its related functions are normal … How to determine the scope of regression test ）、 Exploratory testing （ Test thinking ） Random test

04、 The life cycle of software （ Six stages ）

One 、 Problem definition and planning stage

It mainly determines the development purpose and feasibility of the software , Make a development plan

notes ： Boss 、 The product manager 、 Research and development 、 project manager 、 Demand analysts do

Two 、 Demand analysis / Review stage

Analyze the source （ Prototype map / Software requirements specification ）、 Participants （ host – The product manager , Other participation 、 Research and development 、 Design 、 test ）、 Focus on a problem – Test what is the purpose of participating in this requirements analysis ？（ Enemy and know yourself 、 It's convenient to ask questions ）

3、 ... and 、 Software design stage （ attribute ： It's a development job ）

Outline design （ database surface And other framework things ）

Detailed design （ Pseudo code level ）

Four 、 Software coding stage

Developer tasks 、 Programmers code

5、 ... and 、 Software testing phase

Test Engineer's task or development task

Develop and do ： unit testing 、

Development or test ： Integration testing — The interface test

Testers ： The system test 、

Customer or The product manager ： The acceptance test —Alpha test 、Beta test

6、 ... and 、 Software operation and maintenance stage

edition 、 Product launch （ Version upgrade improvements ）BUG Repair of

05、 Workflow of software testing

One 、 Contact those post personnel

Development 、 The product manager 、 Customer service 、 The implementation of / Technical support / On site implementation 、 The designer

Two 、 The workflow of testing

1、 Test requirements analysis stage ：

Reading needs / Understanding needs 、 Sort out the demand points 、 If you have any questions, you should catch them all , To discuss , Until you figure it out .

2、 Test plan phase ：

A document ： Test leader / The team leader makes a plan

Included content ：

① Purpose ： We have to finish the test , About when to finish , What is the goal .② personnel ： Who's involved , Become a test team .

③ Division of tasks ： Who is responsible for the test of which functional module / Use case writing .

④ Time planning ： When to start writing use cases , When to start testing , When to end the test , When to go online .

⑤ Documents issued ： Use cases ,bug Forms , Software test report .

⑥ Application for resources / Get ready ： Apply for a server ？ What kind of tests do I have to do ？ What kind of tools need to be prepared ？

3、 Test design stage ：

Write test cases ：

① review ： Review whether the use cases are OK Is it complete and correct

② modify ： interpretive error ： correct , Requirements change ： modify

Test execution phase

A smoke test will be conducted before the test （ Pass and continue , Not through , repulse ）、

Execute the test according to the test case ：

① Find out bug– Submitted to the bug Management system

② After development and repair , To verify , Then perform a regression test

4、 Test evaluation stage ：

The test is over , Issue test report ,

If the test passes, go online 、 If the test fails, call back , modify , To test .

Finally, thank everyone who reads my article carefully , The following online link is also a very comprehensive one that I spent a few days sorting out , I hope it can also help you in need ！

These materials , For those who want to change careers 【 software test 】 For our friends, it should be the most comprehensive and complete war preparation warehouse , This warehouse also accompanied me through the most difficult journey , I hope it can help you ！ Everything should be done as soon as possible , Especially in the technology industry , We must improve our technical skills . I hope that's helpful ……

If you don't want to grow up alone , Unable to find the information of the system , The problem is not helped , If you insist on giving up after a few days , You can click the small card below to join our group , We can discuss and exchange , There will be various software testing materials and technical exchanges .

Typing is not easy , If this article is helpful to you , Click a like, collect a hide and pay attention , Give the author an encouragement . It's also convenient for you to find it quickly next time .

Self study recommendation B Stop video ：

Zero basis transition software testing ： Self taught software testing , Got the byte test post offer, Is the B The best video station ！

Advanced automation testing ： Huawei has landed , Salary increase 20K,2022 Most suitable for self-study python Automated test tutorial , Spend it yourself 16800 Bought , Free sharing