1. The difference between software testing and software development

Software development ： The requirement of skills is high, and the degree of professionalism is high , Skill requirements are not extensive

software test ： Skill requirements are relatively broad , But the degree of professionalism is not high

Test interface ：soupUI postman jmeter

Performance testing ：loadrunner jmeter

Automated test scripts ： python java unittest TestNg

​ Charkes fiddler appium

2. The difference between software testing and software debugging

Purpose ：

• Software testing is to verify whether the software has realized the functions it should realize

• Software debugging ： The software developer verifies whether the software realizes the function she wants the software to be the heart

role ：

• test ： By developers （ White box testing ） Work with testers to complete

• debugging ： Done by developers

Stage ：

• test ： Throughout the life cycle of software development

• debugging ： In the development stage

• demand – plan – Design – code – test – Operation and maintenance

The positioning of software testing in different companies

• Project type

• project A project B project C

• Every project has a team

• Performance testing team

• Automated test team

• Security test team

The qualities of an excellent software tester

1. Integration and capability ： communication skills Programming ability Learning ability Ability to describe in words

2. Automated development capability （ Ability to develop automated scripts and tools ）

3. Ability to write test cases

4. Exploratory thinking , Divergent thinking

5. Interest in

6. Responsibility pressure

3. What is demand

demand ---------- Realization （ Software Engineering ）---------- Online use

Requirement is to realize the user's expectation or meet the document （ contract , standard , standard ） Conditions or permissions required

Requirements include two aspects ： One is user demand One is software requirements

The user needs ： Generally, it is roughly summarized

The software requirements ： Software requirements are transformed from user requirements , It is the refinement of user requirements and specific implementation details

Software requirements are the basic basis for testers to test

4.PC End qq Login test cases

1.qq Login test case （ Mind mapping ）------- Test points for requirements

5. The test case

A set of collections initiated to the system under test , Include test environment , Test data , testing procedure , Expected results （ Importance , priority , Mode of operation , Title, etc. ）

The test case ： title ：

Test environment ：xxxx edition PC End xx System

Test data ： user name ：xxxxxx password ：xxxxxxx

testing procedure ：1. Open the mailbox url

​ 2. Enter your username and password

​ 3. Expected results （ The results after the test steps ） Login successful

5.1 Advantages of test cases ：

1. Measure demand coverage ;

2. reusability ;

3. Reference significance ;

4. Can be used for regression testing ;

5. Prevent missing test requirements

6.BUG

If and only if , Procedure specification （ The software requirements ） Existing and reasonable , If the software function does not conform to the software specification , Say it's a software error

When software requirements do not exist , User needs exist and are reasonable , Software functions and user functions do not conform to , It means it's a software error

The stage of software testing ： The whole software development life cycle , Demand stage intervention , Verify the rationality and correctness of the requirements

7. Development model

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

7.1. Waterfall model

start----- Demand analysis ---- plan ---- Design ---- code ---- test —end

characteristic ： Strong stage , Each stage is relatively independent ; Look at the early requirements analysis and later testing

shortcoming ： Testing starts after coding , Lead to problems in the early stage and find them later , You will lose the opportunity to remedy your mistakes

7.2. Spiral model

Suitable for large projects , It's a big risk , Not very clear about the project

characteristic ： Emphasize the test quality and risk analysis of each iteration

shortcoming ： A lot of human and material resources are invested in risk control , It costs a lot

7.3 Incremental model , Iterative model

Four modules of the same system A B C D

Incremental model ：

The first week of development A B Function module

The second week of development C D Function module

Iterative model
The first week is to develop A B C D The basic function of

On top of the other functions of week 1 and week 2

characteristic ： Strong ability to resist risks

7. 4 Agile model

（1）. Individuals and interactions are more important than processes and tools

（2）. Available software is more important than complete documentation

（3）. Customer collaboration is more important than contract negotiation

（4）. Responding to change is more important than following a plan

**PO product owner,** Translate user requirements into user story

SM scrum master project manager , Manage the whole team , Responsible for the smooth implementation of agile processes , All kinds of meeting

ST scrum team People with various skills , Development test UI

Release meeting plan ： The product manager collects requirements to form userstory, Explain , Eliminate the need for iteration development userstory formation sprint backlog

Iteration planning meeting ： Analyze user stories , hold user story Break it down into tasks one by one , Assign developers

Daily station will ： What did you do yesterday ？ Problems encountered ？ Today's plan ？

Product demonstration meeting ： Party a 、 The user demonstrates the product ,PO Make the deficiency userstory, The next iteration improves

Review planning meeting ： Review the whole development process , Find out the deficiencies , Improve in the next iteration , Optimize the iterative process

7.5 V Model

characteristic ：

• 1. The independence of each stage is strong

• 2. Each stage on the left is the basis of the test stage on the right

• 3. And each test phase on the right ----- Stage

Waterfall model variant （ shortcoming ）
Test after coding
Mistakes in the early stage will be found later , You will lose the opportunity to make mistakes in time

7.6 W Model ( double V Model )

characteristic ：
1. Each stage is highly independent
2. Intervene from the beginning of the test
3. It can ensure that the problems in the early stage can be found and corrected in time
4. Test and development go hand in hand

shortcoming ：
1. Each stage is a serial process
2. After one stage is finished, proceed to the next stage
3. Agile development is not supported

8. The life cycle of software testing （ Software testing process ）

Demand analysis ------ test plan ------ Test Development / Design ------ The test execution ------ Test report

Demand analysis ： Analyze requirements , Verify the correctness and rationality of the requirements , Refine requirements , Refine test points according to requirements

test plan ： Determine test scope ; Purpose ; The goal is ; Testers ; Testing tools 、 Time 、 Test environment ;

Test Development / Design ： Develop test cases

The test execution ： The developer has submitted the code , Perform the test perform bug

** Test report ：** The test situation of this iteration is analyzed and summarized . How many test cases have been written ; How many ; How many bug; How many changes have been made , The remaining bug Solutions for ; Test coverage ;

9. What is? BUG

How to describe a BUG？

（1） Test version ( Version number of code submission ) such as git The branch on

（2） Test environment ： The situation is different in different environmental problems ：web System ; Different browsers ; Different versions of the browser ;

**APP**： IOS   Android   Hongmeng   Saipan   windows   ( The version installed on the system )

（3） testing procedure ： Test data and detailed steps to perform the test （ In order to facilitate developers to reproduce the problem ） Repetition problem ： Analyze how the problem arises

（4） The actual result ：

（5） Expected results （ Demand the desired result ）

（6）BUG At the time of production log journal , Error screenshots and other attachments

10 .BUG The level of

（1） collapse

System crash , Can not run , Dead cycle . Database deadlock , Uneven distribution of resources , Black screen , Flash back , Blocking

on-line （ The environment the user uses ） Crash level bug： Go back to the last stable historical version available

（2） serious

The server can use , But it's not stable , Continued use will result in serious errors ; First level menu error , Error inserting user data into database , Threaten the safety of users, etc

（3） commonly

The system can run stably , The secondary function is not realized , The prompt is not perfect , The pop-up box has no close button , Does not affect the user's use

（4） Suggest （ secondary ）

Suggestive , Tips overlap （ can't see clearly ）, The interface layout does not conform to the user's habits , The color does not match the software usage scene

5. bug Life cycle

One bug All kinds of states from nothing

10. The tester because of a bug Conflict with developers , What to do ？

1. Check your own BUG describe , Whether the description is clear

2. It can be considered from the perspective of users , Convince developers

3.BUG The grading should be justified , Compliance with company specifications

4. Testers should constantly improve their professional skills and business level authoritative

5. Ask the product manager to discuss the solution to the problem

How to set up weak network ：

Charles： Set up a weak network

11. Design method of test case

11.1 Use case

1. Design and analyze test cases from an overall perspective

​ Demand based （ Software design documentation ）

​ The user needs ------ Product design and development documents ------ Development ------ test ------ go online

​ user The product manager

​ Business people

（1） Verify the correctness and rationality of the requirements

（2） Analyze requirements , Refine requirements , Decompose test items from requirements , Find out the function according to the test item , Write test cases

11.2 Specific methods of designing test cases

11.2.1 Equivalence class

Equivalence class is to divide the input into several equivalence classes , Take a test case from each equivalence class , If this test case can pass the test , So we mean that this test case represents that the team's equivalence class test passes

Use scenarios ： Test cases cannot be exhaustive , We can't test them one by one

Effective equivalence class ： A collection of data that conforms to program specifications

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

11.2.2 The boundary value

Design test cases according to the boundary of input and output

Test both the left and right boundaries of the value

Effective equivalence class Invalid equivalence class The boundary value （ The highest priority ）

11.2. 3 Cause and effect diagram

When entering a lot , And different input combinations correspond to different outputs , At this time, the causality diagram method is used to analyze the corresponding relationship between different input combinations and outputs

Cause and effect diagram ： Logic diagram Identity And or Not

The steps of designing test cases by causality diagram ：

1. Analyze all inputs and outputs

2. Find the relationship between input and output

3. Draw a cause and effect diagram

4. Draw a decision table

5. Convert the decision table into test cases