General description of test results upload

Created by George I., Modified on Tue, 07 Mar 2023 at 11:40 AM by George I.

Generally, the workflow is the following:
  1. CI's pipeline triggers Allure TestOps' agent
    1. In case of GitLab, GitHub, CircleCI this will be allurectl.
    2. In case of Jenkins this will be the Allure TestOps plugin for Jenkins.
  2. Allure TestOps agent gets the connection params from the settings and triggers build job
  3. Allure TestOps agent starts watching the allure-results folder
  4. Code starts the execution of tests' logic
  5. Tests' logic uses test framework 
  6. Test's logic uses allure framework
  7. Allure framework saves test results
  8. Allure TestOps agent sends the test results in async mode to Allure TestOps

When we say Allure TestOps agent, we usually mean it's either allurectl or Allure TestOps for a certain CI system (e.g. Jenkins, Bamboo).

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article