Is a Build-Forge deployment order. I can imagine that this will be integrated with a uDeploy
When triggered by time, the Execution Console is empty until a few seconds after the set timer.
Figure: The Execution Console when a Test Suite is initiated by time.
RTC Build Completion
With this option RQM "waits" until a build is completed.
Initiate execution as a result of a successful developer-build. The developers can define their own build-structures.
Based on their success we can initiate tests.
Make note of the following:
The build machine is free to run next builds
That a personal build will not trigger a testing cycle!
Developer builds can be setup in such a way that they are only triggered when code is checked in.
Figure: The Execution Schedule overview to set the 'trigger' by a succesful build.
RTC Build Completion & Urbancode
When one references from RQM directly the build, the build must be completed. But tests are executed against
a deployed application. If the build is to be deployed, it will take time.
This option is the solution for that problem.
In the last step of the RTC Build the Urbancode deployment process is started. Within the deployment process
the RQM tests are initiated. Thus these are executed after deployement-completion.