HOWTO¶

General¶

I want to track RHEL-7 and RHEL-8 testcases/requirements separately¶

Use separate branches for RHEL-7 and RHEL-8. For each branch that’s desired to be imported to Polarion, specify the branches in POLARION_PUSH_BRANCHES variable in your deployment.

When the branches are used, they will be taken in account during the import to Polarion. Note that testcases/requirements present in different branches are considered as different from the point of importer and one should not override other one (unless explicitly specified by Polarion ID through special field).

Testcases¶

I want to add a new testcase¶

Create a new file with .tc.yaml suffix anywhere you find suitable in the repository with testcases.

Fill in the file with information about the testcase in format according to Test case.

Check content of the testcase using query.py.

Commit and push changes.

I want to delete a testcase¶

Find the testcase file e.g. using query.py: query.py -t path/to/testcases 'tc.name == "Name of testcase"' 'tc.filename'.

Delete the file.

Commit and push changes.

Note

Deleted testcases are still available in Polarion and are in inactive state.

I want to disable automated execution on all architectures/variants due to issue in automation but I still want to have the testscase tested manually.¶

Change the execution type to “manual” and leave the automation_data. The “manual” workflow doesn’t use automation_data. It may be also good to leave the original execution type commented out so that it’s clear which execution type should be used once the automation is fixed.

Test case cannot be executed due to some testblocker (not tested by the testcase) and there’s no workaround for the testblocker.¶

Add hints about testblockers to the testcase to dedicated field (not implemented yet).

Test case cannot be executed due to momentarily unavailable HW/infrastructure.¶

Add hints about issues to the testcase to dedicated field (not implemented yet).

Test case cannot be executed due to long term hardware inavailability.¶

Example: s390x with specific HDD was not available and is not available for few years already

Remove the testcase from the testplan (either by commenting it out in the list of testcases or via e.g. “disabled” tag and query taking into account such tag).

Test case cannot be temporarily executed on some specific HW subset but can be still tested on other HW variants.¶

Add issue/testblocker hint to dedicated fielt (not implemented yet).

Test case cannot be permanently executed on some specific HW subset but can be still tested on other HW variants.¶

Remove the configuration or create second testcase.

Or

Add issue/testblocker hint to dedicated fielt (not implemented yet).

There are not enough resources for the test plans execution and some test cases have lower priority.¶

Have such testcases executed as part of a different testplan(s) or no testplan at all e.g. by lower priority while having testplans respecting priorities (or by commenting it out of the testplan).

Requirements¶

I want to add a new requirement with specific testcases¶

Follow instructions the same way as when adding testcase, but use .req.yaml suffix and follow requirement structure: Examples.

I want to add link more testcases to requirement¶

Locate the desired testcases and requirement e.g. by using query.py.

Look for verified_by field and modify its content.

When direct-list is used, add name of the testcase to the list.

When query is used, modify the query so that the desired testcases match the query. You can use query.py to see effect of the changed query: query.py -r path/to/testcases 'req.name == "My requirement"' 'req.verificationTestCases'

Commit and push changes.

I want to delete a requirement¶

The same applies here as when deleting testcases.

Note

Deleted requirements are still available in Polarion and are in inactive state.

Note

The inactive requirement in Polarion loses all references to testcases as it cannot be tracked anymore.

Testplans¶

TBD

Misc¶

I want to find some specific testcases/requirements¶

Use query.py to look for desired testcases/requirements. To find information about testcase properties, see testcases.structures.testcase.TestCase or testcases.structures.requirement.Requirement respectively.

Example: query.py -t path/to/testcases '"Hello" in tc.tags' 'tc.filename'.