Execution of all the test scripts

Hi Amit,

There is a concept of test suite that you might want to explore. Test suite contains test cases.
For your case :
Create a test suite 1 and add test case 1 with a script 1. Again Add test case 1 with test script 2 to test suite 1 and so on.

Hope this helps.

Thanks
Pranam

Hi Amit- Conceptually the idea is that a test case represents what needs to be tested and the script (or scripts) are how it is tested. Why do you have multiple test scripts associated with the same test case? Is it to support different platforms (test environments) or for some other reason?

Tks,
Paul

Hi
I am trying to create test scripts that are generic and which can be used in multiple test cases.
The system doesnt prevent me from adding multiple test scripts to a test case so I went ahead with this idea.
Thanks
Amit

Hi Amit- Conceptually the idea is that a test case represents what needs to be tested and the script (or scripts) are how it is tested. Why do you have multiple test scripts associated with the same test case? Is it to support different platforms (test environments) or for some other reason?

Tks,
Paul

Hi
I am trying to create test scripts that are generic and which can be used in multiple test cases.
The system doesnt prevent me from adding multiple test scripts to a test case so I went ahead with this idea.
Thanks
Amit

You may want to take a look at keywords. They allow you (at least in manual scripts) re-use common steps in other scripts. So for example if you have a set of common script steps for login or logout you can create keywords for those and include them in other scripts.

The idea with allow multiple test scripts per test case is to support different scripts per platform (linux vs Windows for example) or other differences which require a different implementation of a script to test the same test case. Staying aligned with that model will make reporting on test coverage, and requirements coverage much easier.

Tks
Paul

Hi Amit- Conceptually the idea is that a test case represents what needs to be tested and the script (or scripts) are how it is tested. Why do you have multiple test scripts associated with the same test case? Is it to support different platforms (test environments) or for some other reason?

Tks,
Paul

Hi Paul
Thanks for setting me on the right part.I had a idea about the keywords.But the way I was implementing it was incorrect.
Thanks ones again
Amit Sharma

Hi Paul,

I worked with keywords. I found that if you have more than one verification/reporting point for a keyword and we execute the script associated with this keyword then we can mark the whole keyword as Pass or Fail in one step.

If there is a scenario where in the keyword steps one verification point is pass and the other is fail then how can we mark that as Fail. Does it mean that a keyword should not contain more than one verification/reporting point.

And if this is so will the keyword concept be useful to amit

Thanks,
Alka

Hi, not sure which version you are running, but Keyword behavior changed between 1.0 and 1.0.1 to become more flexible. In RQM 1.0, a keyword forced a verification point at the end so that each keyword had to be marked as pass or fail. Starting in 1.0.1, you can have multiple verification points within a keyword, or none at all, e.g., if it is a setup step and does not need a verdict. So I would give 1.0.1 Keywords a try to see if they are useful for what you are trying to do. Thanks.