Add Tests for Execution
I am setting a new Test Cycle or a Test Suite, that I can go add all those Test Cases we just created.
If I’d like, I can schedule some of these to be executed against that agent that we just created by selecting the more option. Now, this value is showing up because I have an automation host and an agent set up for this project. I only have one agent configured for this project but if I had more, I would set it right here through the scheduling window. Since the automation host is set up to poll, I could wait five minutes, I could click Poll Now, or I could go to the host service and click “Run All Now”.
Debug Scheduled Runs
What you can see now is I just scheduled this job with those three tests. I can see the status as “Not Run” and that one agent that was configured. So let’s go ahead and run the test and see what happens.
Check Run Logs
So, behind the scenes, this is the service that’s still running. I can check out the logs, so I can see if it’s started and if the scheduling worked or not. I can see that this job, specifically, failed, so now I can go and debug it since this is the first time I ran it. I have something configured incorrectly with the Java class, so I’m gonna go ahead and pause this and fix that pack.
I got everything running, and now I want to show this scheduling from the beginning. Select the tests you want to run, and set the frequency to run one time.
Now they’re scheduled for execution. I got all the configuration set up. If I look in qTest Launch, I can see this new job that I have scheduled. It’s not run yet, so let’s go ahead and just trigger it right now. You notice the status is “Running” which means the tests are being executed on the host machine.
Now they’ve been updated back in qTest Manager and we see the latest test results.