2013 R1: The new distributed execution environment

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 07 May 2014 13:27 by Jing

Jing

Created on: 11 Jul 2013 20:32

Type: Feature Request

2013 R1: The new distributed execution environment

I'm trying to see the new distributed execution environment. Here are some questions:
How to schedule 10 lists at one time?
For example, I have about 60 lists; I just want them to run one after another on the test server, since I don't exactly know how long each test list run takes, it's impossible to schedule them one by one.

How the "Distribute test among these machines" works? 
The tests inside one list will be distributed?

Thanks for the answer in advance.

8 comments

Jing

Posted on: 12 Jul 2013 18:15

Thanks a lot Jared!! As a summary of my feedback, (no sure how other user use this feature), My team use the list like ordered list in Visual studio, the test inside a list has to be run on one machine. 
I hope there is more document explain the expected way to use the schedule feature, personally I really wish this feature can work like how visual studio deals with coded UI test:  I setup some test agent (execution server for test studio), assign all of them to one test controller(schedule service for test studio), connect the controller to my visual studio (connect the schedule service to my standalone test studio), and when I select run all my test remotely, I don't care how many test agents (execution servers) I have or who they are , the controller (schedule service) do assign the test list, balance the workload, each test server run one list at a time. 
when I realize the test takes too long time to run, I will request more VMs, I get these new VMs, install test agent(execution server for test studio) and register them to the single test controller(schedule service for test studio), so next scheduled test run or manual triggered test run will have more test list running parallel.

ADMIN

Jared Twing

Posted on: 12 Jul 2013 16:23

And since I am posting from my phone autocorrect mangled the word each up there. :)

ADMIN

Jared Twing

Posted on: 12 Jul 2013 16:21

Correct. If your test list has ten tests inside of it and you have ten execution servers racha server will be given one test to run and they will all run at the same time. 

If you uncheck the distribute box all ten servers will get all ten tests to run. 

Thanks for checking out the beta! We really appreciate your feedback.

Jing

Posted on: 12 Jul 2013 14:33

I see. Thanks Jared.
just one more uncleared thing for me, if I can only schedule one list at a time, what exactly it means when the system give me the options to "Distribute test among these machines". if I have 10 test servers registered under one schedule service, the test cases inside that One test list gets distributed?

ADMIN

Jared Twing

Posted on: 12 Jul 2013 14:24

Gotcha. There is no schedule groups of test lists, but I think it is a good idea. 

For now you can achieve the same result by scheduling each list individually at times that are ascending in the order you want the lists queued. 

So list one queued at 11:00 and list two at 11:05, etc. 

Assuming list one takes longer than five minutes to run. List two will run as soon as execution servers are available.

Jing

Posted on: 12 Jul 2013 13:45

BTW I'm making all WPF desktop application tests...

Jing

Posted on: 12 Jul 2013 13:43

That's exactly what I want, "be able to schedule each list after each other"
but when I select more than one list, the schedule testlist button disabled. So I don't know how to schedule all the lists I have.

ADMIN

Jared Twing

Posted on: 12 Jul 2013 12:03

Each execution server can run one web test and be an agent for one load test at ang one time. 

Since the Scheduler works as a queue you should be able to schedule each list after each other and that will run them all back to back as the execution servers are ready.

If you are using multiple execution servers then distribute will send one web test at a time to each server from the queue.