question

Scheduling jobs ---- iTest provides the ability to define jobs which are scheduled to run at some specified starting time and recurrence. These jobs may then be executed from within iTest and monitored via the iTest Jobs view. However, the most likely scenario for the use of scheduled jobs is within a headless regression environment where it is not practical to keep an instance of the iTest application open. For these situations it is necessary to use itestrt. Defining scheduled jobs is not the subject of this HOWTO. However, the process is quite simple, consisting of selecting File/New/Job and filling out the wizard. It is possible to define jobs that will executed immediately, as well as non-recurring jobs. When attempting to execute a scheduled job via itestrt, those two types of jobs are not well suited. It is preferable for a job to either be scheduled to start sometime in the future or be recurring. Once defined, it will be necessary to export the projects that contain the test cases and other dependent files that the scheduled job needs. This will create ITAR files that itestrt can then use to execute. The scheduled job is itself defined in a file with the `.ffjd` suffix. This file may itself be exported within an ITAR, or you may choose to make it accessible to itestrt on the file system by copying it somewhere easily accessible. Running scheduled jobs with itestrt ---- Once your job description (.ffjd) file has been created and all the required ITAR files have been exported and placed in a directory you may launch itestrt to executed the scheduled job. The general syntax is: itestrt --itar --job If all ITAR files had been placed in /home/user/itars and the job named “RunTests” defined in the file /Jobs/RunTests.ffjd in iTest project “my_project” was also exported in the my_project.itar file, then the proper command line would be: itestrt --itar /home/user/itars --job project://my_project/Jobs/RunTests.ffjd itestrt will show a table of jobs that are pending to be run. Once they begin execution, each job will show output appropriate to the type of type of job being executed. If a test case is being executed, the output will be the same as if the test case were being directly executed from the itestrt command line. Once the job is complete, itestrt will remain running until there are no more scheduled executions of the job. Multiple Jobs --- Multiple jobs can be executed from one instance of itestrt simply by supplying itestrt with multiple --job arguments. For example: itestrt --itar /home/user/itars --job project://my_project/Jobs/RunTests.ffjd --job project://my_project/Jobs/WeeklyRegression.ffjd