Shulou(Shulou.com)06/03 Report--

LR Learning Notes I. The basis of software testing

1. The concept of software: the combination of programs and documents.

two。 The concept of software defect: refers to the error of computer hardware, software system or application software, that is, BUG.

1) causes of hardware errors: design errors and aging failure of hardware components

2) the cause of software error: caused by design error in software development enterprise.

3. The concept of software life cycle: from the definition and generation of software requirements to the abandoned life cycle.

ii. Definition of software testing

1. Testing: including hardware testing and software testing

two。 Test case: designed for the relevant functional description and system implementation in the requirements specification for testing input, execution conditions and expected output. The test case is the smallest entity to perform software testing.

3. Test environment:

1) hardware environment: (PC, laptop, server, minicomputer, mainframe, etc.)

2) Software environment (operating system, web application server (tomcat, WebLogic, IIS, WebSphere, etc.), database, other software (office software and antivirus software, etc.), browser)

3) Network environment (local area network, metropolitan area network or Internet)

4. What you need to pay attention to in setting up the test environment:

1) try to simulate the real scene of the user (network application, software, hardware usage environment)

2) Clean environment

3) there is no influence of virus

4) independent test environment (testing and R & D are separate)

iii. Classification of software testing

1. Black box testing (functional testing, data-driven testing, specification-based testing)

two。 White-box testing (structural testing, logic-driven testing, testing based on the program itself)

Methods:

1) statement coverage: each statement in the program is executed at least once

2) decision coverage: each decision in the program is true or false at least once

3) conditional coverage: enable each condition in the decision to obtain a variety of possible results.

4) decision / conditional coverage: satisfying both judgment and conditional coverage

5) conditional combination coverage: such that various possible combinations of conditions in each decision appear at least once.

3. Static testing: the process of not running the software under test, but statically checking the program code, interface, or documentation for possible errors.

4. Dynamic testing: actually run the software under test, input the corresponding test data, and actually check the output results.

5. Unit testing: unit testing is the minimum granularity in the testing process, which closely tests the functions and modules of the product according to the program framework, including entrance and exit parameters, input and output information, error handling information, partial boundary numerical testing.

6. Integration testing: the system testing technology of the team leader software, which assembles the modules that pass the unit test together according to the design requirements, and carries out a comprehensive test in order to find all kinds of errors related to the interface. Including methods: non-incremental integration and incremental integration.

7. System testing: system testing is carried out after the integration test, using black box testing technology completely.

8. Acceptance testing: after the system testing is completed, the final confirmation test of the software can be performed.

1) Alpha testing: refers to the testing of upcoming software products (alpha versions) by people within the software development company who simulate all kinds of user behavior.

2) β test: the software version adjusted by α test is β version, and the software development company organizes typical users in all aspects to actually use β version in their daily work.

9. Regression testing: when testing a new version of the software, repeat the test case used in the previous version test

10. Smoke testing: the object is every newly compiled version of the software that needs to be tested squarely in order to confirm that the basic function of the software is normal and that subsequent formal testing can be carried out.

11. Random testing: in testing, the data is generated at random.

iv. Software testing process

1. Test plan: describe the test work to be completed, including the background, objectives, methods, resources, schedule, test organization, and risks associated with the test.

two。 Test design: design test cases and test data to ensure that test cases fully cover test requirements

1) Test case classification:

Functional test cases: including functional testing, robustness testing, and reliability testing

Security test case

User interface test case

Install / uninstall test cases

Integration test cases (including interface tests)

Performance test cases (including performance test, load test, stress test, capacity test, concurrency test, configuration test, reliability test, failure test)

2) Test case design method

Equivalence class division method

Concept: black box testing method, which divides a large number of test data into several equivalence classes: effective equivalence class and invalid equivalence class.

Principles for dividing equivalence classes:

Divide by interval

Divide by numerical value

Divided by numerical set

To divide by restrictions or rules.

Boundary value analysis

Boundary value analysis

Concept: design test cases based on boundary conditions

Select test case principles:

If the input condition specifies a range of values, you should take the boundary value that has just reached the range and the value that has just exceeded the boundary of the range as the test input data.

If the input condition specifies the number of values, the maximum number, the minimum number, one more than the maximum number and one less than the minimum number are used as the test data.

If the data fields or output fields given by the specification of the program are ordered collections (such as order tables, sequential files, etc.), the first and last elements of the collection should be selected as the test case.

If the program uses an internal structure, the boundary value of the internal data structure should be selected as the test case.

Causality chart method

Concept: the final result of the causality diagram method is the decision table.

The test case generation steps are as follows:

Analyze which are the causes and results in the specification of house arrest requirements, the reason is the equivalence class of data conditions or output conditions, and the result is output conditions.

Analyze the semantics described in the software requirements specification, find out the corresponding relationship between cause and result, cause and cause, and draw the causality diagram according to these relations.

Indicate the constraints.

Convert the causality diagram into a decision table.

Design test cases for each column in the decision table.

Decision table

Concept: a way to analyze and express situations where different operations are performed under multiple logical conditions.

Conditional piles: list all the conditions of the problem

Action pile: list the actions that may be taken according to the problem

Conditional items: list the values for conditional piles

Action item: lists the actions that should be taken in the case of various values of the condition item.

Steps for establishing decision table

Several conditions are involved in analyzing and determining the problem.

Analyze how many value spaces there are for each condition

Draw the conditional value analysis table. Various possible combinations of analytical conditions

Several decision schemes are involved in analyzing and decision-making problems

Draw the decision table of conditional combination

Determine the decision-making scheme for the combination of various conditions, that is, fill in the decision rules

The merger simplified decision table, that is, whether there are conditions that do not need to be determined for the combination of conditions corresponding to the same decision scheme.

Error inference method

Scene method

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.