It's all about the answers!

Ask a question

What is the real purpose of test case regarding test script?


Christophe Tournier (361107) | asked Feb 18 '10, 6:06 p.m.
Since we can associated several test scripts to a test case but executed in a suite only one script per test case, what is the purpose of test case? Why not launches directly the test script within the test suite?
Is it for selecting for example a manual script instead an automated script? Is it for selecting a specific way to do the same thing?

6 answers



permanent link
Patrick Van Zandt (1.2k1) | answered Feb 26 '10, 1:29 a.m.
JAZZ DEVELOPER
A test script is very specific in the sense that it says "search Google for IBM and verify that you get the expected result".

A test case allows you to define what exactly you are testing for, why you are testing, what is the associated risk, etc.

http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/c_testcases.html
A test case answers the question, "What am I going to test?" You develop test cases to define the things that you need to validate to ensure that the system is working properly and is built with a high level of quality.

permanent link
John Nason (2.4k1012) | answered Mar 03 '10, 7:57 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Good points Patrick.
Another thing to keep in mind is decoupling the functionality and actions from the particular environments. I might have a Test Case for "verify search functionality" and need to run scripts to do so on 3 different environments like Firefox, Chrome, and IE. The Test Execution Record maintains that correlation between the Test Case, Environment, and Script.
Regards,
John Nason

A test script is very specific in the sense that it says "search Google for IBM and verify that you get the expected result".

A test case allows you to define what exactly you are testing for, why you are testing, what is the associated risk, etc.

http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/c_testcases.html
A test case answers the question, "What am I going to test?" You develop test cases to define the things that you need to validate to ensure that the system is working properly and is built with a high level of quality.

permanent link
Christophe Tournier (361107) | answered Mar 10 '10, 8:47 a.m.
Thanks four replies. What was surprising is the fact that the questions raised from HPQC users... It seems sometimes for them that RQM is more complex because of that specific concepts

permanent link
Sterling Ferguson-II (1.6k12288273) | answered Mar 10 '10, 1:06 p.m.
Thanks four replies. What was surprising is the fact that the questions raised from HPQC users... It seems sometimes for them that RQM is more complex because of that specific concepts


This is exactly why our HPQC users refuse to go.

They connect to DOORS and CQ. They can see a test that failed directly from QC. But if they use multiple scripts in RQM per test case, they one script may fail, but the others may pass. It does not seem that there is a way to differentiate this using DOORS/RQM...

permanent link
Sterling Ferguson-II (1.6k12288273) | answered Mar 10 '10, 1:42 p.m.
Thanks four replies. What was surprising is the fact that the questions raised from HPQC users... It seems sometimes for them that RQM is more complex because of that specific concepts


This is exactly why our HPQC users refuse to go.

They connect to DOORS and CQ. They can see a test that failed directly from QC. But if they use multiple scripts in RQM per test case, they one script may fail, but the others may pass. It does not seem that there is a way to differentiate this using DOORS/RQM...

Sorry, to be clear, in QC they can see

test script1 (with Requirement) = pass
test script2 (with Requirement) = pass
test script3 (with Requirement) = fail

on RQM, if we have these 3 test scripts under one test case. the report is

test case = pass

permanent link
John Nason (2.4k1012) | answered Mar 10 '10, 4:42 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Wait, where specifically are you seeing this? That just seems wrong on our part.
Thanks,
John

Thanks four replies. What was surprising is the fact that the questions raised from HPQC users... It seems sometimes for them that RQM is more complex because of that specific concepts


This is exactly why our HPQC users refuse to go.

They connect to DOORS and CQ. They can see a test that failed directly from QC. But if they use multiple scripts in RQM per test case, they one script may fail, but the others may pass. It does not seem that there is a way to differentiate this using DOORS/RQM...

Sorry, to be clear, in QC they can see

test script1 (with Requirement) = pass
test script2 (with Requirement) = pass
test script3 (with Requirement) = fail

on RQM, if we have these 3 test scripts under one test case. the report is

test case = pass

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.