Requirement-based testing (RBT)

Requirement-based testing (RBT)

Chen nengtech

2007-7-25

 

The primary responsibility of testers is to find bugs, but the most important and fundamental responsibility should be to ensure that the company's software products meet customers' needs before the software product is released.

 

The test group uses RBT (requirements-based testing). The requirement-based test method makes the test more effective because it enables the test to focus on the root cause of quality problems.

 

According to the research report, for many years, most software projects cannot be completed as planned and cost cannot be effectively controlled. The primary cause of most project failures is poor software quality, resulting in a lot of rework, redesign, and coding. The two major causes of poor software quality are: incorrect specification of software requirements and coverage of problematic system tests.

 

Error in Requirement Specification

We often hear end users complain that we don't need our software, and these software has passed rigorous testing and QA. We will not be surprised at this because we know that the demand is wrong from the very beginning.

 

A survey (James Martin ("an Information Systems manifesto," Prentice Hall, 1984) showed that 56% of defects were introduced in the software demand phase. 50% of these requirements are caused by problems, unclear, unclear, and incorrect document writing. The remaining 50% is due to missing requirements.

 

Problematic test coverage

It is difficult to obtain satisfactory test coverage. In particular, the current systems are complex, with many functional scenarios and many logic branches. It is almost impossible to completely cover them.

Furthermore, demand changes often lack control, and there is often a lack of traceability between requirements and test cases.

 

RBTThree best practices

1,Test early and often. Early test, frequent Test

Confirm the Business Value of the requirement.

All stakeholders should review the requirements.

Use Cases to check the integrity of requirements

The application of language analysis technology ensures that the requirement documents are clear and consistent, so that different people have different interpretations of the same issue.

 

2,Test with your head, not your gut.Do not test with experience alone

Do not rely on the experience of testers to design test cases. Instead of relying on the skills of experienced testers, you should adopt systematic and rigorous test case design methods. This method is used to increase the validity of test coverage. Formatted and structured requirement documents help testers evaluate the test coverage rate of a requirement.

Check the errors in the test case through test case review, and identify the deficiencies in the requirements.

 

3,Test with measurement and improvement in mind.Maintain measurement during testing

In the process of using demand-based testing methods, it is very important to maintain traceability of requirements. Keeping traceability between requirements and test cases and tests helps to monitor the progress and measure the coverage rate. Of course, it also helps to control demand changes.