Forum Discussion

Raju_Vusirikala's avatar
Raju_Vusirikala
Contributor
17 years ago

Test Scenario

Hi

We have developed all the testcases required to our product, How do I define only specific test cases needs to executed for specici scenario like smoke test, regression testing, clientX Release Testing. Instead of disabliing/Enabling TestSuites and TestCases in TestRunner.

If you have any such feature that will help us in defining the test scenario and execute those. instead disable/enable every time. And missing few things in that process.

Thanks
Raju.
  • omatzura's avatar
    omatzura
    Super Contributor
    Hi Raju,

    Unfortunately there is no better support than what you describe, ie enabling/disabling testcases/teststeps via scripting. A TestScenario feature has long been planned, but just isn't available yet.. sorry..

    regards,

    /Ole
    eviware.com
  • Hi Ole,

    It will be greate if you suggest any work-around for this like can we  specify in Groovy Script the test cases needs to be executed,

    As we can able to  execute any single test case from project,  like that i need to configure set of those single testcase as one collection for specific scenario and execute that collection.

    I will apreciate any work-around solution for this. only conern is we need to define at one time, and execute those instead of disable/enable dynamically while executing TestRunner.

    Thanks
    Raju.
  • omatzura's avatar
    omatzura
    Super Contributor
    Hi!

    maybe you could create a seperate TestCase for each of your "scenarios" containing only Run TestCase steps that run the desired TestCases? From the command-line you could then run the specific TestCase with the corresponding options..!?

    regards,

    /Ole
    eviware.com
  • BPerdok's avatar
    BPerdok
    Occasional Contributor
    Hi eviware Team,

    I’m very interested in these topic. Has there something happend in that way?

    Best regards,
    Barend Perdok
  • Hello,

    Sorry, I don't have any thing new regarding this. For now the best approach is still the one Ole described, i.e., having separate TestCases with a number of Run TestCase steps.

    Regards,
    Dain
    eviware.com