Execute tests in a single project on 2 slaves
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Execute tests in a single project on 2 slaves
I have a project with 100 tests. I have a master project which runs all the tests in this project on a remote VM.
ProjectSuite
+ Project01
+ Master
+ NetworkSuite
+ Job01
+ Task01 - Project01 (100 tests - 1-100) - VM01
I would like to add another task to Job01 to run half the tests in another VM.
+ Master
+ NetworkSuite
+ Job01
+ Task01 - Project01 (50 tests - 1-50) - VM01
+ Task02 - Project01 (50 tests - 51-100) - VM02
What will be the best way to achieve this?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
IIRC, Tasks can be associated to test items within the project. Create a 2 test items in your project, split the test cases to be child test items of those two test items then assign the parent test items to your tasks.
Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff
----
Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.
Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apologies if I am not understanding correctly, but by "child test items of those two test items", do you mean using the "Run Keyword Test" action? If yes, will the log show the tests stats of 50 tests separately? Won't it just combine everything and tell me 1 test passed or failed?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Go to View -> Organize Tests. What shows up in there are called "Test Items". You can create a "tree" of them with parent and child Test Items, groups which are more like folders, etc. If you organize your test items that way, they will show up as individual pass/fail in your test log.
Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff
----
Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.
Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please ignore the above message. I found "New Child Test Item" in "Test Items" tab of the project. I will try that and post back. Thanks!
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried <Project>\TestItems\<TestItem> in the task and got a "not found" error.
The "Editing Task Properties" page lists only keyword tests, script routines, low level procedures, project and "no value" as possible values. How do I specify the parent test item in a task?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So, a test item can be specified in the command line as detailed in TestComplete Command Line (thanks @tristaanogre, @cunderw).
/project:project_name /test:test_name
test_name can be a test item. But specifying a test item in the "Test" field in a network suite task is not working. Can someone please confirm whether a test item can be specified in a task or not?
