General description of test results upload

Created by George I., Modified on Thu, 05 May 2022 at 11:05 AM by George I.

Generally, the workflow is the following:

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.
Allure TestOps agent gets the connection params from the settings and triggers build job
Allure TestOps agent starts watching the allure-results folder
Code starts the execution of tests' logic
Tests' logic uses test framework
Test's logic uses allure framework
Allure framework saves test results
Allure TestOps agent sends the test results in async mode to Allure TestOps