The testing process pays too much attention to functional testing

1. Definition:

Too much emphasis is placed on functional testing rather than test quality, data, and interface requirements. And test the constraints of architecture, design, and implementation.

Second, the period of occurrence

Non-functional requirements.

Third, trap performance

1. Most tests focus on verifying functional performance

two。 There is no appropriate level of verification of quality characteristics (e.g. availability, reliability, robustness, security, security, ease of use)

3. Test engineer, reliability engineer, safety engineer, human factor engineer did not perform relevant professional test types (for example, did not perform * test)

4. The deficiency levels of various quality characteristics and their attributes are identified only after the system has been delivered and put into operation.

IV. Negative consequences

1. The test cannot verify whether the system has important quality characteristics and meets all relevant quality requirements.

two。 It is confirmed that the data and interface requirements cannot be met until later in the integration or after delivery

3. The delivery of the system is delayed and fails to meet a large number of unacceptable non-functional requirements.

Fifth, reasons

1. Test plans and process documentation do not fully take into account test non-functional requirements.

two。 Non-process requirements require specialized testing of non-functional requirements

3. Management, R & D and testing believe that:

(1) testing other types of requirements (data, interfaces, quality and architecture, design, implementation, or configuration constraints) is difficult.

(2) apply methods other than testing (analysis, review and review) to verify quality requirements

(3) it takes too long to test these non-functional requirements because of their cross-nature.

(4) compared with functional requirements, non-functional requirements are not very important.

(5) non-functional testing will occur naturally as a by-product of testing functional requirements.

4. Other types of requirements (quality requirements)

5. Functional testing is the only test specified in the development contract.

VI. Suggestions

1. Prepare for

Fully consider test non-functional requirements in test plans and process documentation

Include process requirements in the contract and enforce professional testing of non-functional requirements

two。 Enable

The importance of ensuring that management, development, and testing understand non-functional requirements and comply with architecture and design (through white-box testing)

3. Execution

Fully perform other types of testing

4. Verification

(1) determine whether management, development, and testing understand the importance of testing non-functional requirements and compliance with architectural design, implementation, and configuration constraints

(2) determine whether the quality engineer has verified that the tester tests non-functional requirements and constraints.

(3) determine whether test non-functional performance is fully taken into account in test plans and process documentation.

(4) determine whether to measure, analyze, and report types of non-functional defects.