Software testing learning - day one

One 、 Cognition test

What is software testing

answer ： Use technology methods verification Whether the software meets the requirements

The purpose of software testing

answer ： With the least manpower , material resources 、 financial 、 Find problems in the software and fix 、 To reduce business risk

（ The software is bound to have defects ）

characteristic ：

• Job vacancy ⼝：⼤

• Salary ： objective

• ⾏ trade ： Stable （ Not subject to back-end development language ⾔ Limit ）

• ⼊⻔ Simple

Two 、 Mainstream testing skills

1. A functional test

2. automated testing ：

   Use code or tools instead of manual verification of project functions

3. The interface test

4. Performance testing

   Simulate multiplayer Software , Find server defects

3、 ... and 、 Tests often ⽤ classification

By stages

1. unit testing ： For the program source code ⾏ test （ Development ） White box testing
2. Integration testing ：⼜ call Pick up ⼝ test , Mainly aimed at Modules and modules or System and system Between Pick up ⼝ Into the ⾏ verification
3. The system test ： For software all ⾯ Into the ⾏ verification （ function 、 compatible 、⽂ files ）
4. The acceptance test ： send ⽤ Internal measurement 、 Public beta to achieve
   • Internal measurement ： Inside the company ⾏ test .α Test internal test
   • Public survey ： Let players enter ⾏ test . β Test public beta

The code can ⻅ Degree division

1. ⿊ Box test ：⼜ Call it functional test （ Not at all ⻅ Program source code , Only for functions ⾏ verification ）
2. Grey box testing ：⼜ Weighing connection ⼝ test / Integration testing （ Look No ⻅ Part of the code ）
3. ⽩ Box test ：⼜ Scale unit test （ For the program source code ⾏ test ）

automated testing , In theory, it belongs to black box test Actually, it belongs to functional testing

1. System testing and ⿊ Box test focuses on nuclear ⼼ yes A functional test
2. Integration test and grey box test ⼜ call Pick up ⼝ test
3. Unit tests and ⽩ The box test is right Code Into the ⾏ test
4.⾃ Automation test attribution A functional test
5. Performance testing 、 Safety test attribution Special tests

Expand - The test strategy

Smoke testing ： Before large-scale testing Verify the main function of the program , Ensure that the program is testable

Face time question ： What is the test standard ？— Smoke test passed What to do before testing ？----- Smoke testing

Four 、 Model

Quality model

（ Learn about any software or hardware , Test areas to cover ）

The quality model provides the basis for test design Different angles of view And verification direction

 a key ： function 、 compatible 、 performance 、 Easy to use 、 Security 

Software quality model （ISO/IEC 25010）

1. Functionality ： The function meets the needs
2. Performance efficiency ： The performance meets the actual requirements
3. Compatibility ： The software can be compatible with mainstream hardware and software
4. Ease of use ： Easy to use
5. reliability ： Reliable performance and function application
6. Information security ： The degree of security of information during transmission or storage
7. Maintainability ： Easy to maintain
8. Portability ： With migration and convenience

W Model

What to learn ？ – Software development process 、 The role of software testing in the development process ⽤

Development process ： Demand analysis 、 Outline design 、 Detailed design 、 code 、 Integrate 、 The implementation of 、 deliver

Testing process ： Unit test design 、 Integration test design 、 System test design 、 Acceptance test design 、 unit testing 、 Integration testing 、 The system test 、 The acceptance test

5、 ... and 、 Testing process

1、 Demand analysis

2、 test plan

3、 To write ⽤ example

4、 Of board ⾏⽤ example

5、 Defect management

6、 Test report

1. Demand analysis ：

    In front of ： Read the requirements analysis document   Record ambiguities 
   

   • Ensure that all departments have a consistent understanding of requirements
   • Stand in different perspectives on the needs （ Leak filling ）

2. Plan preparation

    What to measure ： Test objective and scope 
   
    Who will test it ： Personnel schedule 
   
    How to measure ： The test strategy 、 Testing tools 
   

3. Test case design

    explain ： Documents for designing and executing tests 
   

4. Use case execution

    explain ： Documents for performing tests 
   

5. Defect management

    explain ：--> Submit --> verification --> close 
   

6. Test report

    explain ： Test target 、 Testing process 、 Defect statistics 、 Defect analysis 、 Test summary 
   

6、 ... and 、 test ⽤ example

What is a test case ？

It is the execution document designed for the test project

 Use cases ： User cases 
 The test case ： Documents for performing tests （ User cases ）
 Consideration point ： Quality model （ function 、 performance 、 compatible 、 Easy to use 、 Security ）
 effect ： Prevent missing measurement 
      Implement test standards 

Format （⼋⼤ elements ）：

• Use case number ： project + modular + Number
• Use case title ： Expected results + Operation steps
• modular / project ： Project or module
• precondition ： To execute this use case , And those pre operations
• priority ： Indicates the importance or influence of the use case P0~P4（P0 The highest ）
• testing procedure ： Describe the operation steps
• Test data ： Operational data , If not, it can be empty
• Expected results ： Expected results

How to design test cases

Different scene and demand , There are different use case testing methods , You need to learn how to design use cases

Statement ： Is to learn the dark horse test tutorial , If you are interested, you can click the link to learn Learning entrance