For manual tests, the only source of the data available is the data the end users entered using Allure Testops UI.
For the automated tests, generally there are two sources for the metadata available:
from test result
used by default for automated tests
Allure Testops takes all the metadata (test attributes if you like) from the test results uploaded to launches and updates the test cases with the metadata from the test results
from test case
less common but still a viable option when some of the attributes of automated test cases are managed manually in Allure Testops UI
this requires manual work and manual control of the metadata relevance
For example, a test engineer wants the information about the description to be more precise and generally extended comparing to the information received from the test results:
To do so, you need to set up the test results upload policies.
Setting up meta data update policies
To perform the actions described below, you need to have Owner permissions in the project you are working on.
To explicitly define what should be source of the metadata for a certain project, you need to perform the following actions.
Jump to Project's Settings.
Then proceed to the Upload section.
and then hit Create to create your very first metadata update policy.
Then select an attribute (part of the tests' metadata) field for which you need to create the update policy.
Select the policy defining the source of the data.
And save the policy by pressing Submit button.
From this moment on,
Allure Testops will allow entering configured attribute (in our example, the description field) values via UI.
the attribute description will be taken from the test case information stored in Allure Testops database, and information from the test results will be ignored, i.e. in a test result associated with a certain test case Allure Testops will show the data from the test case.
Fields allowing creation of an update policy
Currently, Allure Testops supports the creation of upload policy for the following fields:
Peculiarities of working with certain attributes
precondition and expected_result
Attributes precondition and expected_result are for manual tests only, these are not provided from the test results, therefore if you for some reason want these attributes to be kept in the test cases after your manual tests were automated, you need explicitly set the metadata update policy for these attributes to from_test_case before the automation of such tests, otherwise the data will be deleted by the system on the launch closure.