Theoretical basis of Software Test engineer (I.)

Software engineer Theory basics and how to write test cases (with login interface and QQ Personal Chat Interface for example)

Software Testing

definition: manual or automated run or test process test cases

Goal:

1. Ensure software Quality

2. Providing information

3. Ensure the development process

object: program + all process documentation (feasibility report, project implementation plan, software Requirement Specification, System function specification, outline design manual, detailed design specification, etc.)

Principle:

1. Early and continuous

2.pareto principle

3. Not all software errors can be fixed, but it is still possible to submit all bug-wrong documents

4. From small to large

5. Avoid developers testing their own code

6. Traceability to customer requirements

7. Every modification is tested

8. Save all Document Records

Method ( category ) :

Unit Test---> Integration testing---> System testing---> Acceptance testing

Static testing, dynamic testing

Functional Testing: Logic functional testing, interface testing, usability testing, installation testing, compatibility testing

Performance testing: General, stability, load, pressure

Regression test

Smoke test

Random test

software life cycle: design, development, and success

Software life cycle including software development and software testing

Model:

Waterfall Model: products with stable demand

V Model: test development parallelism

　　　　　　　　

Progressive Model:

Test Flow: Test Report-Test plan-testing, test execution, test planning, test plans, requirements review

Test Design: Decomposition test object –> Define test case--build requirement coverage--design test steps

use case writing (use Case number, use case name, use case level, preconditions, test step, expected result, post condition, comment, author)

Attention:

1. Title Plus Black

2. Show border

3. Interface use case writing from top left to bottom right

4. Identify specific terms (e.g. button positions)

5. The test steps correspond to the expected result one by one

6. A post condition refers to a possible use case after the use case

7. Ambiguous words (such as: etc.) cannot appear

8. Consider as many scenarios as possible

9. Avoid excessive mouth hydration

Theoretical basis of Software Test engineer (I.)