Ask a Question

Running my test in Execution Plan more then once

SOLVED
gshipp
Occasional Contributor

Running my test in Execution Plan more then once

I have a set up 20 test cases that are in multiple folders (for example I have one called Log_in at the high level then 4 sub test). I then have a total of 3 high level folder like this. all the test take about 15 min to run from end to end. My question is: have can I run these same test over and over again? The scenario would be that I want to run this set up test all night.

3 REPLIES 3
vinniew
Staff

Hi @gshipp 

 

You could periodically schedule this or invoke a loop. 

 

I have to ask tho, given it takes 15mins to complete and provide you with the feedback you need;

 

By running this all through the night, from a functional test perspective what are you looking to achieve? 

 

KR

 

Vinnie 

gshipp
Occasional Contributor

The reason for continually running them is to stress the system. 3-4 hours would probably be more accurate. This are all UI test (not scripts) mostly using OCR steps (this product is not smart enough and has no objects).

 

1) How can i put this in a loop when I am running them from the Execution Plan.

2) I like the idea of scheduling a time to run the test. How and where would I be able to do that?

Hi @gshipp 

 

In the execution plan there is a count tab option. 

 

You can set the number of counts(iterations) per item

 

My advice would be to use a test item/folder structure and place the count there. 

 

Anthing within that folder/test item will execute and re-execute based on the number of counts 

 

For periodically scheduling it may be done via a CICD or scheduler tool  

 

See https://support.smartbear.com/testcomplete/docs/testing-with/running/scheduling.html

 

https://support.smartbear.com/testcomplete/docs/working-with/integration/continuous-integration-syst...

 

on the stress testing part, what exactly is it that you are stress testing? 

 

What kind of application is it? 

 

I might be able to assist further on how best to approach this as simply reiterating or looping over time may not provide the needed results to effectively stress test your application

 

KR

 

Vinnie

cancel
Showing results for 
Search instead for 
Did you mean: