Overview - Jobs

Jobs

Jobs section of a project in Allure TestOps stores the information about all build jobs associated with current project, i.e. if any build job sent the tests results from CI side to this project, you will see it here.

if you see this write to support.qameta.io

Managing jobs

Job actions

Job action button invokes 2 actions:

  1. Job configuration
  2. Job deletion

if you see this write to support.qameta.io

Job configuration

To start using the job for creating Launches form Allure TestOps UI, you need to configure the build job:

if you see this write to support.qameta.io

  1. Assign CI server with appropriate credentials.
  2. Mark the Job as available for running tests on it.
  3. Link the ENV variables received from the job to the global environment variables. This can be updated later on.
  4. Submit the changes.

After this operation you can use this job to start test on certain CI server.

Update job from build server

When you click on the button Update job from build server, Allure TestOps will refresh the information about the default Environment parameters and update the Job accordingly to the retrieved information.:

  1. List of environment variables will be updated.
  2. Default values of the Environment variables will be updated.

if you see this write to support.qameta.io

Running jobs

Clicking on the Ruin job button will invoke the launch creation dialogue and launch start will invoke the starting the tests assigned to a certain job.

if you see this write to support.qameta.io

This command will run full job by default, i.e. all the tests associated with this job will be added to new launch and Allure TestOps will create testplan.json with all the test IDs and full names and will provide this file to CI server for execution.

if you see this write to support.qameta.io

Once you’ve created a launch for your job, you need to proceed to Launches section to analyse the test results.