Forum Discussion
AlexanderM
14 years agoStaff
Hello Michael,
Chuck is right about the prioritization - though the Forums are managed, this is the place for our users to talk to each other and share information.
To get a reply sooner, it is recommended to open a support ticket with us directly.
As for the problem you are having:
We have recently seen a similar problem. It occurred in a situation when the Master project had too many jobs and tasks.
So, if this is the case for you, please see the recommendations below. We are working to fix the problem, but there are no time frames so far.
The values that can be used in the "Copy remote log", "Action after run", "Use previous instance" and "Remote application" columns of the Excel file can be found in the help topics below:
Task.CopyRemoteLogMode
Task.ActionAfterRun
Task.PriorInstanceMode
Task.RemoteApplication
The script routine above is a routine that retrieves data from a data storage - the Excel file. Such a test concept is known as a data-driven test. You can find more information in the Data-Driven Testing - Basic Concepts and Using DDT Drivers help topics.
Chuck is right about the prioritization - though the Forums are managed, this is the place for our users to talk to each other and share information.
To get a reply sooner, it is recommended to open a support ticket with us directly.
As for the problem you are having:
We have recently seen a similar problem. It occurred in a situation when the Master project had too many jobs and tasks.
So, if this is the case for you, please see the recommendations below. We are working to fix the problem, but there are no time frames so far.
Here are the recommendations:
Try reducing the number of jobs (tasks) to avoid the problem. However, if the jobs (tasks) you have are an essential part of your test, and you can't easily change their number, I recommend that you implement the following approach:
1. Make your project have only one job containing only one task.
2. Create an Excel file that is to contain task properties (host, test, etc.).
3. Execute your distributed test from script - assign the needed properties to your task and start the execution. Upon completion, change the properties to match the next test, and run the execution again.
function test()
{
var Driver = DDT.ExcelDriver("C:\\Task.xlsx", "Sheet1", true);
var task = NetworkSuite.Jobs.ItemByName("Job1").Tasks.ItemByName("Task1");
while (!Driver.EOF())
{
task.Host = NetworkSuite.Hosts.ItemByName(aqConvert.VarToStr(DDT.CurrentDriver.Value(0)));
task.ProjectPath = DDT.CurrentDriver.Value(1);
task.CopyRemoteLogMode = eval(DDT.CurrentDriver.Value(2));
task.ActionAfterRun = eval(DDT.CurrentDriver.Value(3));
task.Test = DDT.CurrentDriver.Value(4);
task.PriorInstanceMode = eval(DDT.CurrentDriver.Value(5));
task.RemoteApplication = eval(DDT.CurrentDriver.Value(6));
task.Run(true);
Driver.Next();
}
}
The values that can be used in the "Copy remote log", "Action after run", "Use previous instance" and "Remote application" columns of the Excel file can be found in the help topics below:
Task.CopyRemoteLogMode
Task.ActionAfterRun
Task.PriorInstanceMode
Task.RemoteApplication
The script routine above is a routine that retrieves data from a data storage - the Excel file. Such a test concept is known as a data-driven test. You can find more information in the Data-Driven Testing - Basic Concepts and Using DDT Drivers help topics.
Related Content
- 7 years ago
- 13 years ago
Recent Discussions
- 2 days ago
- 2 days ago
- 6 days ago