Metadata update settings

Sources of the metadata

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 QA 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.

1. Open your project.
2. Go to Settings → Upload.
3. Click + Create.
4. Select an attribute (part of the tests' metadata) field for which you need to create the update policy.
5. Select the policy defining the source of the data.
6. Click Submit.

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 attributes of test cases:

• name
• test_layer
• description
• expected_result (please read the last section on this page)
• link
• tag
• issue
• member
• custom_field

Peculiarities of working with certain attributes

expected_result

The attribute expected_result is for manual tests only. This attribute is not provided from the test results. Therefore, if for some reason you want to keep this attribute in the automated test cases after your manual tests become automated, you need to explicitly set the metadata update policy for this attribute to from_test_case before the automation of such tests. Otherwise, the data will be deleted by the system upon the launch closure.