mjwatkins2
Occasional Contributor
Joined 7 years ago
User Profile
User Widgets
Contributions
Re: Running test suites via distributed testing
I got around this issue with a loop (below) that runs each task one at a time remotely, running a new task when a previous task completes. This lets you assign multiple tasks under the same job to the same host (I am distributing a couple hundred tests across a dozen hosts with this method). Sounds like what you need. The following code assumes you have already created a job with a long list of tasks, with multiple tasks assigned to the same host. You can do this programmatically. function RunJob(jobName) { // keep track of the Task row number for each host var runningHosts = new ActiveXObject("Scripting.Dictionary"); // run through the list of tasks and begin the first one for each host var tasks = NetworkSuite.Jobs.ItemByName(jobName).Tasks; for (var i = 0; i < tasks.Count; i++) { var task = tasks.Items(i); var hostName = task.Host.Name; if (task.Active && !runningHosts.Exists(hostName)) { runningHosts.Add(hostName, i); task.Run(false); } } // periodically check the list of tasks and see if one is finished var done = false; while (!done) { aqUtils.Delay(60000); var hostNames = runningHosts.Keys().toArray(); for (var j = 0; j < runningHosts.Count; j++) { var hostName = hostNames[j]; var lastTaskIndex = runningHosts.Item(hostName); var lastTask = tasks.Items(lastTaskIndex); if (lastTask.State == ns_Idle) // is the last task for this host finished? { // find the next task for this host and run it var i = lastTaskIndex + 1; for (; i < tasks.Count; i++) { var task = tasks.Items(i); var taskHostName = task.Host.Name; if (task.Active && taskHostName == hostName) { runningHosts.Item(hostName) = i; task.Run(false); break; } } // check if this host is finished with all tasks // if so, remove it from the dictionary if (i == tasks.Count) { runningHosts.Remove(hostName); if (runningHosts.Count == 0) done = true; break; // jumps back to the while loop } } } } }1.2KViews0likes0CommentsRe: Run test items in a group
Thanks for the reply, Alex. For your first suggestion I think you are referring to calling each individual test's main script function in sequence from some wrapper, and then executing the wrapper (right?). We've traditionally done something like this but it causes all sorts of problems when tests fail or when the tested application fails. Better to run each test as its own test item, I think. For your more flexible approach I'm missing something. The key line from the code you refer to is "RunProjectTestItem" which seems to be only available in COM. You're suggesting to call this from a job. So the master PC's job runs a task on a host VM using TestExecute, the job's task calls an external COM function with RunProjectTestItem, which then launches another instance of TestExecute to run the test item? That's the part I'm confused about -- wouldn't I need to run two instances of TestExecute to make that happen? Best, Matt477Views0likes0CommentsRe: Run several test projects on a host during parallel testing
I've read the documentation several times but no dice. Which is surprising, really, it seems like running several tests sequentially on one remote host would be a common use case for parallel testing. I've also searched the forums here and read several posts about external custom solutions that have been developed to run particular tests on particular machines, but I'm trying to avoid hacks and fragile custom setups. I think posting screenshots of my setup will be more confusing than helpful, as I'm part of the way through an upgrade of an older TestComplete system (using a complex web of batch files to run tests across VMs) to what I thought was going to be a nice parallel testing use case for the NetworkSuite.1KViews0likes1CommentRun several test projects on a host during parallel testing
Hello all, In the NetworkSuite editor I can assign only 1 test per task to each host. Is there a way or a workaround for running multiple tests or test projects on each host? Suppose I have 6 projects with script tests and 2 remote hosts. On one host I want to run all the tests in 2 projects and on the other host I want to run all the tests in 4 projects (the 2 take as much time as the 4, so both hosts will finish at the same time). I don't see any nice way to do this. Or really any way to do this at all. Since I can only assign one test to a host in a Task, I thought I would try assigning a script to each that runs the appropriate projects sequentially. But you cannot run projects from scripts, so this idea failed. The only other idea I have is to create one project per host and then assign the project to the corresponding job Task. In the project I would have to add all the scripts from other projects and then call each script one-by-one. This is not a practical solution. Understand that my example with 6 projects and 2 hosts is a simplification of many projects with many scripts and hosts for a much larger project. Plus, the idea of creating one project per host immediately feels like a bad design. Also, in case it matters, we're using JScript for this project. Thanks!1KViews0likes3Comments