Overview - Launches


This section covers the information about Launches section.

All the information about the test results is stored in Launches section.

Launches section UI overview

The main screen of Launches section provides the following information about the ongoing and finished launches as well as allows filtering the launches and manually upload the test results.

Launches information

Allure TestOps provides the following information about launches:

  • Launch name
    • either generated by Allure TestOps tools in CI side
    • or generated on Allure TestOps side
    • or entered manually by a person that initiated a Launch
  • Current status of a Launch
    • Open
    • Closed
  • Current status of the job run on CI side
    • including the hyperlink to build job
  • Number of tests with the distribution by execution status (Passed, Failed etc.)
  • Launch’s tags
  • Environment data
    • VCS branch
    • browser used to run tests
    • host’s address where tests were executed
    • etc.

if you see this write to support.qameta.io

Launches information filtering

Search (or filtering) across all the available launches is activated by clicking on the funnel icon in the upper right corner.

Filtering is supported by using all the meta information about the launches, e.g.:

  • Launch name
  • Build job name
  • Marker of automated build
  • Link to an issue in issue tracker
  • Date and time of launch
  • Environment data
  • Launch’s tags

if you see this write to support.qameta.io

Test results manual upload


First of all why could we need it?

Say, you are in the process of the automation of a test case and you need to check if your test is generating the results as you expect. You can upload the results, check the representation of the information and delete the launch created by the manual upload.


There was an interruption caused by the network and results weren’t uploaded. So, you can upload the tests results manually as and emergency workaround.


In upper right corner click Upload button.

In the modal dialogue that will be opened fill the following data (any and all of this data can be omitted but you won’t be able to filter/find these test results):

  1. Name. Name your launch or leave blank and default naming will be applied.
  2. Add launch’s tags (smoke, manual, delete etc. - your choice).
  3. Add links to an issue in issue tracker if this is related to some task you are checking.
  4. Add links if any.
  5. Add environment data if this information is important.
  6. Add the test results either using drag and drop or select from the disk.
    1. Result files - upload all files from your test results folder, i.e. select all and drag to the drop area.
    2. Archives - archive your test results and then upload zip archive.

if you see this write to support.qameta.io

Test results format

Following test results format are supported at the moment:

  • allure1
  • allure2
  • cucumberjson
  • jgiven
  • junit
  • trx
  • xctest till xcode 11, newer versions are working via adaptor
  • xunit
Test results file size limitations

If a test results file exceeds 3 megabytes it will be processed by Allure TestOps as an attachment.

Test documentation for manually uploaded test results

To create test documentation (test cases) you need to close the launch for manually uploaded test results. If you don’t want to create the test cases for manually uploaded files, you need to delete manually created launch.

State of a launch

Each launch can have 2 states either open or closed.

Allure TestOps will process test results and generate Test Cases (aka test documentation or live documentation) only when a launch is closed.

Open launch

Launch can be in an open state in the following cases:

  • The transfer of test results to Allure TestOps is in progress, i.e. build jobs is still running.
  • The team is still analysing the test results and resolving the errors in the test results.
  • The team either forgot to create automates closure rule or forgot to close a launch manually.

Closed launch

Allure TestOps will finally process the test results only for a closed launch, which means the following:

  • Test documentation (the content of Test cases section) will be either generated for new test cases or updated for the existing ones.
  • Test results will be used to calculate statistics
  • Test results will be used in analytics and can be viewed in dashboards.

Closing a launch

There are two ways to close a launch

  1. Manual closing
  2. Automated closing
Closing a launch manually

To close a launch you need to click Close launch button.

if you see this write to support.qameta.io

Closing a launch automatically

Setting for automatic launches closure are made on a project level.

  1. Go to the project settings (you must be an owner of a project to see this section).
  2. Go to launches.
  3. Edit the settings for Auto close policy

if you see this write to support.qameta.io