Software Testing Problems
Follow Poor Requirements

How Poor Requirements Cause Software Testing Problems

A common software testing situation is that testers are given requirements that they must interpret and then build their test cases. This is a time consuming, labor intensive, manual effort.

Another problem is that the testers interpret the requirements independently from the developers who also interpret the requirements. There are "software testing" problems when their interpretations vary.

Another problem is lurking underneath the interpretations of developers and testers. Does either group validate their interpretation with the customer? All too often the answer is "No".

The more detailed and unambiguous the requirements are the less interpretation in needed by both developers and testers. The more ambiguous the requirements are the more interpretation is needed with a greater chance of divergence of those interpretations.

Is There a Better Way?

Yes, there is!

Discover and document requirements using the Building Requirements Consensus™ Methodology with Blueprint's Requirements Center (opens in new window) analyst tool. The methodology plus Requirements Center are the Building Requirements Consensus™ Approach.

People from various perspectives including: business customer, technical architect, developer and QA tester (opens in new window) can review and have significant input into the requirements before they are finalized and development starts.

This means that as people engage in the requirements they naturally understand what the application is designed to do and why. They are building clarity and consensus.

It is a common developer complaint that they do not know what the business is trying to accomplish. The Building Requirements Consensus™ Approach approach helps answer that complaint.

Automatically Generate Tests

One of Blueprint's Requirements Center capabilities is that it automatically generates test scenarios! They guarantee 100% coverage of every use case scenario that has been documented in Requirements Center - automatically.

You can print the tests to use them manually or you can export them to testing tools.

Tests Import Seamlessly into Test Suites like HP Quality Center

Requirements Center tests import seamlessly into test suites like HP Quality Center. This is a major time savings compared to manually writing tests!

Additionally, you can be assured that the tests do in fact test the requirements as written. This is because the tests are generated directly from the requirements. They are not interpreted.

Even using HP Quality Center, testers will have work to do. They must decide what kind of tests to run for each scenario. Do they want a positive test, a negative test or a boundary test? They add data to the automatically generated scenarios to produce test cases.

Note this Important Distinction

The scenarios match the requirements and they are generated automatically at the touch of a button. Literally!

From Software Testing to Building Requirements Consensus™ Home