It's all about the answers!

Ask a question

Test Artifacts Structure

Vincent Leon (3468) | asked Mar 23 '13, 2:44 a.m.
 We are implementing RQM first time in our project.

We already have manual scripts in word docs. Our existing structure is 3 levels:

Testsuites - TestCases - Test Scripts

But in RQM, (as per my prevoius experience) its a best practice to link one manual and one automation script to RQM for execution and reporting purposes. That makes it possible to only 2 levels, Test Suites and Test Cases. 

What is the best way we implement our existing structure (3 Levels) in RQM? Can we attach multiple test scripts to one test case. If we do that, can we do reporting at test script level?

One answer

permanent link
Marc van Lint (852129) | answered Mar 23 '13, 4:18 a.m.
Hi Vincent,

The hierarchy in RQM is simple:

A test plan references test cases.
A test case has a specific test goal.
A test case references multiple test scripts (e.g. a simple one with less verification points, one with a lot of verification points, automated version etc). But all covering the same goal!

This structure is stable.

Now you can add to your plan iterations (when) and environments (where).

The next step is to define 'test-tasks', these are called TestCaseExecutionRecord (TCER). These TCERs say who should execute what, when and where!! A great thing!! This way you can plan and you can report on it.

Now in the execution tab you can find these 'todo's of test execution (when they are manual). You can execute and you get a test execution result. You might want to change end-result add a defect on it etc.

Try to create above strucure and run a test and see how your TCER (live) reports are updated!

Within RQM you have also the artifact Test Suite. This suite references TCERs. And in a similar way you can execute them that way. I'm sure you will figure it out.

Additional tip: A testplan references a requirements collection, a test case reference a requirement.

Bad approach is to have one test case and add multiple test scripts to it, like a testscript to open the application,  and other script to run a happy path and an other script to close the application. You can 'nest' scripts using Manual Testing keywords (or when automated callscripts). It won't give you an option to report on individual test results (because reporting is done on test case execution level).
Additionally if you create 3 tc with appropriate testscripts which start, run happily, close application and put them in a suite you create a test case dependancy. It's oke, but some test-specialists don't like that. A test case should be independant from other tc. There is some logic in it.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.