Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

This post will explain, how you can schedule test cases written in vREST. vREST do not provide direct support for scheduling test cases on its own server. But you can easily schedule test cases written in vREST with the help of any external schedular like cron.

Here is a video tutorial for the same:


Prerequisite for the machine, on which you want to schedule test cases.

Let's take a sample application (Contacts Application) and step by step guide on how we can schedule vREST test cases.

Note: You can find the source code of sample application at Github.

Step by Step Guide:

Step 1: Write your automated test suite in vREST

First you need to write test cases for your test application in vREST to ensure the build quality of your web application. Then copy the test case list URL by clicking on button "Copy Current Test Case List URL" available in Continuous Integration section. You can find the test cases for this sample application in vREST here

Step 2: [Optional] Learn how vrunner command works and get your hands dirty on it by installing it locally first

First setup the vrunner module by following the guide Setup / install vrunner.

Once you setup this module on your local machine, you can execute the vREST test cases by executing the following command:

vrunner --email=<EMAIL_ID> --password=<PASSWORD> --url=<URL OF vREST Test Cases> --logger=xunit [--filepath=<absolute log file path>] [--env=<ENVIRONMENT>]


  • email: Email ID through which you have registered on vREST
  • password: Password of your vREST account
  • url: Provide the test case list URL here. You can find the test case list URL by going to your vREST instance and select Test Cases tab. Now click on button "Copy Current Test Case List URL" available in Left hand side, below the "Filters section". Provide the copied URL in this option.
  • logger: Use xunit here. Reporter xunit will export the test case report in xml junit style, which can be used in any continuous integration server to publish the reports.
  • filepath: Absolute path of the log file, into which execution process and result logs will be dumped. If path/file is not present, tool will try to setup that path, and create file automatically. Please note that if file already exists, that will be overwritten. By default it will be the `vrest_logs/logs.xml` in current directory.
  • env: [Optional] Provide the environment name which you have defined in vREST (Case-sensitive).

Step 3: Add the above vrunner command in any external schedular

Now, you can add this vrunner command in any external schedular like cron. That's it.

For example, if you want to schedule vREST test cases daily at mid night, then you may write the cron job like this:

0 0 * * * /path/to/vrunner --email="<VREST_EMAIL>" --password="<VREST_PASSWORD>" --url="<VREST_TEST_CASE_LIST_URL>" --logger="json" --filepath="<ABSOLUTE_LOG_FILE_PATH>"


  1. In VREST_TEST_CASE_LIST_URL, every % symbol must be escaped with backslash (\).
  2. In your environment, path to vrunner can be found with the following commands (in Linux / Mac):
    1. which vrunner
  • No labels