The growth path of software testing

Examination ：【 software test 】 Quickly conduct software testing _ Pi Pi Yao HAPPY The blog of -CSDN Blog

1. What is software testing

Testing is to verify whether product features meet user needs （ Or it is the requirement document formulated by the product personnel ）

Software testing runs through the whole software development cycle ,

        Review of preliminary requirements documents

        The medium term involves test cases and consistency testing

        Submission and closing of post issue forms

        etc.

2. Software testing process

1. Review of software requirements specifications ----（ The purpose is to eliminate ambiguity 、 Perfect the details 、 Reach a consensus ）

2. Write the test plan according to the requirements document

3. Write test cases according to requirements documents

4. Perform the test （ find bug、 Submit bug、 Regression tests, etc ）

5. Test report

3. The basic elements of software testing

1. The software UI Interface tests     -----（ Is it beautiful 、 Compliance with design specifications

2. Function test of software      -----  （ Test whether the functions of the software can be used normally

3. Software performance test    ------（ Test whether the software can maintain stability in a specific environment

4. Software security testing   ------（ Test whether there are security problems in the use of the software

5. Software usability testing   -------（ Test the software experience , Is the user experience good

6. Software compatibility testing   -------（ Test whether the software can be compatible with different environments during use

Take the login test of mailbox as an example ：

1. UI Interface tests ：----- （ Whether the form is reasonably designed , Whether the picture interface is beautiful

2. A functional test ：

        2.1 Enter the correct user name 、 password , Test login successful

        2.2 Enter the correct user name 、 Wrong password , Test login failed

        2.3 Wrong user name （ User name is too short 、 Too long 、 The user name is empty ）, The right password , Test login failed

        2.4 Wrong user name （ User name is too short 、 Too long 、 The user name is empty ）, Wrong password , test

3. Performance testing ：--------- Tens of thousands of people log in at the same time , The response time should not be higher than s？

4. Safety test ：------- Whether the password is encrypted or not 、 Whether the password can be copied 、 Capture packets to see if the password can be transmitted in plaintext

5. Ease of use test ：------- Whether the user test experience is good

6. Compatibility test ：-------- Different operating systems , Different browsers 、 Different resolutions 、 Different devices

4. Test phase classification

1. unit testing ： After developers develop a function module , Unit testing is to test this code

2. Integration testing ： After unit testing , Developers combine the unit modules that have been tested to form a “ assembly ” , This assembly will be tested

3. The system test ： The tester tests the whole system

4. The acceptance test ： Tests performed by users , The content of the test is similar to that of the system test , Test whether the developed software meets the requirements of the requirements document , Whether it meets the needs of users .

5. Write a test plan

1. Test range ： Determine the functional and non functional requirements of the test

2. Test environment ： Software environment 、 Hardware environment

3. The test strategy ： Selection of test tools 、 Key points and methods of testing

4. Test management ： Allocation of test tasks 、 Schedule 、 Communication methods

5. Test risk ： Do not thoroughly understand the requirements document 、 It is estimated that the test time is insufficient 、 The test execution is not in place

6. Design test cases

1. Carefully analyze the requirements document , Mining and analyzing details , And use case design for these details

2. Design test writing documents

        2.1 Use case number

        2.2 Test items / Test scenarios

        2.3 Test case title

        2.4 priority

        2.5 Preset conditions

        2.6 input data

        2.7 Operation steps

        2.8 Expected results

3. Design method of test case

Reference resources ：

(72 Bar message ) Detailed explanation of test case design method _ Li XiuXiu's blog -CSDN Blog _ What are the test case design methods

1. Division of equivalence class

2. Boundary value analysis

3. Decision table method

4. Cause and effect diagram

5. Orthogonal experiment

7. Software testing methods

White box testing ：

1. Code checking

2. Static structural analysis

3. Logical coverage

4. Basic path testing

Black box testing ：

1. Division of equivalence class

        In all test data , Data set partition with certain characteristics .

        1.1 Effective equivalence class ： A collection of data that meets the needs

        1.2 Invalid equivalence class ： Data sets that do not meet the requirements

2. Boundary value analysis

3. Wrong guess

4. Decision table method

5. Cause and effect diagram

6. Orthogonal experiment