Feed on
Posts
Comments

Recall the post about improving Vendor written SOWs? The message was to first document your requirements and second ensure there was a thread from Requirements to the Work being performed by the Vendor. Note: this doesn’t just apply to Vendor written SOWs but your own as well. Now, let’s take that concept of creating a thread another step – threading requirements to test cases.

For every requirement, there must be a test case to validate the requirement  has been delivered and it functions as required. And vice versa, the test cases created must align with a requirement, else why were they written – wasted effort, wasted dollars. If the numbers are not very large – not a lot of requirements, a single tester, short testing period – the record keeping is manageable with basic tools and without becoming too sophisticated (word processor, spreadsheet). But when requirements number into the hundreds or thousands, a test team of more than one person, testing which will last for several months, time to move on to more sophisticated processes of testing and methods of record keeping.

To start with, it is highly recommended to number your requirements. This makes the record keeping and reporting simpler to manage. As an example, TR001 for Technical Requirement 001, FR003 for Functional Requirement 003, etc.

There are tools that align to this discipline and can make the job easier for you – tools that permit recording of Business Requirements, alignment with Test Cases, test results, the ability to produce a variety of reports on test results and even a test results dashboard.  The benefits of centralized tools are that the Quality Assurance / Testing team, the projects managers and any other stakeholders invited to monitor testing progress can do so by viewing the testing dashboard at their discretion.

If you don’t have the tools or the budget, roll your own. While this will require a tad more manual effort, the discipline can still be applied.  There is the option to use a spreadsheet, or if the mood strikes you, create  a database, which would provide the ability to produce a broader range  of  and more flexible reports.

If you are fortunate to have the budget to purchase tools, or would to know what to budget for, there are a number to choose from.  There are tools to document requirements, test cases and defects, and that provide the thread across them all. There are also guidelines for integrating tools from different vendors, if that’s what you have inherited. We suggest performing a search on the following tools (Mercury, ClearQuest, RequisitePro, TestDirector, WinRunner, LoadRunner) to find out what is available.

Happy Testing!

One Response to “Thread Your Project Requirements To The Test Cases”

  1. PM Hut says:

    Hi Joe,

    I have published an elaborate article about the statement of work. Hope you and your readers will find it useful.

Leave a Reply