Hi,
I have more than 200 Test Suite in a Test Collection.
These Test Suite contains many Tests Cases.
These Test Suite must be executed in this specific order.
It would be easier to manipulate with the possibility to “plan” the execution of several Test Collection without console mode
→ I can continue my job, resolving this ticket can boost my performance
HI @Joeyxx
I don’t quite understand yet. What’s the problem with the current Test Suite Collection ? Can you elaborate more on your use case.
You can create multiple Test Suite Collections.
If you want to execute your Test Suites in 2 types of sequence, then you can do so by creating 2 TSC.
If you want to execute your Test Suites in 5 types of sequence, then you can do so by creating 5 TSC.
Having multiple TSC is enough to express your “plans”, isn’t it?
If you have several TSC, you must manually run TSC1 then TSC2, etc…
I want to run TSC1 then TSC2 automatically, but without console mode.
In my KS project, I have to run TSC2 many times during a test campagne, by night :
TSC1
TSC2
TSC3
TSC4
TSC5
TSC2
TSC6
TSC2
Today, I have something like this :
TS1
TS2
TS3
TS4
TS5
TS2
TS3
TS6
TS7
TS2
TS8
TS9
TS10
TS3
…
TS200
TS2
TS3
OK, possibly I understand your problem.
You need one more layer of control how to compose the testing modules.
Therefore you’ve got an idea of adding a layer which can compose a sequence of TestSuiteCollection. However, I would like to point out that you have another possible way of adding a layer of module composition.
As you possibly know, a Test Case can call other Test Cases by WebUI.callTestCase():
You can replace a Test suite with a combination of “Caller Test Case and Callee Test Cases”. With this tool in your hand, you can drastically refactor the structure of your project.
Let me assume, you already have a Test Suite “TS1” which comprises 3 Test Cases “TC1” + "TC2 + “TC3”. Then you can add a new Test Case named “CallerA” which executes the callee test cases “TC1” + “TC2” + “TC3”.
Please note that the CallerA can do the same as what TS1 does.
You can replace all of your existing test suites with caller test cases:
| Your existing Test Suites | -> | equivalent Caller test case |
|---|---|---|
| TS1 | -> | Caller1 |
| TS2 | -> | Caller2 |
| TS3 | -> | Caller3 |
| … | … |
And then, you can transform (re-implement) your existing Test Suite Collections into Test suites. Each Test Suites will call the Caller test cases which will indirectly execute the Callee test cases.
| Your existing Test Suite Collections | -> | refactored to new Test Suites |
|---|---|---|
| TSC1 | -> | nTS1 |
| TSC2 | -> | nTS2 |
| TSC3 | -> | nTS3 |
| TSC4 | -> | nTS4 |
| TSC5 | -> | nTS5 |
Once done, all of your existing Test Suite Collections will be migrated to a set of new Test Suites.
Then you have got a room of introducing new series of Test Suite Collections. Your new Test Suite Collection can execute any combination of nTS1, nTS2, nTS3 … automatically in a designed sequence.
Hi @ThanhTo ,
@kazurayam explain my request far better than me :
“You need one more layer of control how to compose the testing modules.”
