It's all about the answers!

Ask a question

How should we structure a large testing project using Rational

Ryan Lavorgna (811) | asked Jan 28 '14, 4:38 p.m.
retagged Jan 31 '14, 4:17 p.m. by Dejan Custic (2855)


Our Project is trying to set up testing scripts for a very large testing effort on a project and having a large amount of difficulty using Rational tools.

Here's a summary of our current setup:

Test Script: Houses a series of steps to accomplish a functional task (Login, click through 3 screens, see output form, run report, logout)

Test Case: pretty much a useless shell to hold 1 test script (needed to link requirements)

Test Suite: Logical grouping of scripts that cover the same area of the application

Test Plan: the Phase of Testing e.g. Integration Test

Our problem is that we need to associate Testing Conditions (requirements) with the step level of test scripts. in the example above, if the report doesnt work, i need to show that the condition around the report fails (when the step fails), but the other conditions associated (say login for example) work. This seems impossible in Rational.

So I was going to try the following:

Test Script 1: Login steps

Test Case 1: Holds Test Script 1 (Linked to Login Requirement)

Test Script 2: Screen 1 steps

Test Case 2: Holds Test Script 2 (Linked to Screen 1 Requirement)

Test Script 3: Screen 2 steps

Test Case 3: Holds Test Script 3 (Linked to Screen 2 Requirement)

Test Script 4: Screen 3 steps

Test Case 4: Holds Test Script 4 (Linked to Screen 3 Requirement)

Test Script 5: logout steps

Test Case 5: Holds Test Script 5 (Linked to logout Requirement)

Then make a Test Suite that holds Test Case 1-5 from above and sequences them in order with Execution Order (no idea how to set this). The Test Suite qould be called: Test Group 1

there would be multiple suites all grouped under a Test Plan: Which would cover something like "Intake"

Multiple test plans would work together to create full scenarios of testing using the Test Suite Naming to make sure teh correct scripts are run in order.

It's a huge work around, but so far we've just found Rational incredibly difficult.

Please advise (also please suggest whether this will break the canned reports)



Ara Masrof commented Jan 28 '14, 8:07 p.m.


You may be interested in the following Plan Item implemented in the upcoming 4.0.6 release:
Plan Item 74532: Traceability to test script step test improvements

Ryan Lavorgna commented Jan 28 '14, 8:18 p.m.


Thanks, this is helpful, but still doesn't really get me where i need to be. We are using version of RQM and i cannot link requirements to steps of a script even though Plan Item 74532 which you reference says that in RQM v4 users can link script steps to requirements.

Is there a guide on how to do this as we have not been able to create this linkage.



Accepted answer

permanent link
Ara Masrof (3.2k15) | answered Jan 28 '14, 8:41 p.m.
Try this:
Online Help V4.0

Testing > Developing test cases, test suites, and test scripts > Developing manual test scripts
Creating manual test scripts

The Validates column displays requirements that are associated with test script steps. You can add requirements traceability to individual steps by either of the following methods:
To link steps to requirements that are associated with the test case, at the far right, in the Requirement View, scroll down to view associated requirements; then drag individual requirements to test script steps.
To link steps to any requirements associated with the project, in the Action Menu, click Link to any requirement.
Note: For the Validates column to be available, the project administrator must have enabled linkage between requirements and test script steps via Manage Project Properties > Test Script Preferences. 
Ryan Lavorgna selected this answer as the correct answer

Your answer

Register or to post your answer.