...
These tags determine when a test runs. Some tests might be ran at multiple frequencies.
Avocado Tag | Description |
---|---|
| Ran in CI for every PR. These are generally small core tests. |
| Ran in CI once daily. These are generally less critical than |
| Ran in CI weekly. These are generally less critical than |
| Manual tests for special purposes. These tests might: not run in CI, require special configuration, be for specific environments. |
| SOAK tests are ran manually at specified intervals. |
| Ran when deploying a new DAOS installation. |
List of Stage/Environment Tags
These tags determine where a test runs. Each test should only have one set of these tags.
Avocado Tag | Description |
---|---|
| Tests that are ran on the Functional Hardware Medium stage. |
| Tests that are ran on the Functional Hardware Large stage. |
| Tests that are ran on the VM Functional on [CentOS, Leap, Ubuntu] stages. This tag is usually not specified explicitly. Instead, the lack of a |
Anchor | ||||
---|---|---|---|---|
|
These tags group tests by common Features. The list recorded here is a starting point, and is likely to be incomplete or out-of-date. When evaluating which tag(s) should be used in the Features: pragma, remember that the tests themselves define the available set of tags, and can be consulted for hints as to which tags are likely to provide the best coverage for the PR.
Avocado Tag | Description |
---|---|
| Verifies |
| Verifies |
| Verifies |
| Verifies |
| Verifies |
| Verifies Data Mover utilities. Additional sub-tags:
|
| The |
| Verifies |
| Verifies DAOS on a newly deployed system. |
| Verifies |
| Verifies DFS. incomplete |
| Verifies |
| Verifies |
| Verifies HDF5. incomplete |
| Verifies |
| Verifies the |
| Verifies |
| Verifies |
| Verifies online and offline |
| Verifies features related to |
| Verifies |
| Verifies |
| Verifies catastrophic recovery. |
| Verifies |
| Verifies |
| Verifies |
| Verifies |
| Verifies |
Anchor | ||||
---|---|---|---|---|
|
...
Short Answer
This helpful utility will tell you the minimal tags that represent all tests in a given file(s):
Code Block | ||
---|---|---|
| ||
cd src/tests/ftest/
./tags.py list pool/create.py
PoolCreateTests |
Long Answer
Each test is uniquely tagged with its method name and the test class it belongs to. For example, from ftest/pool/create.py, the :
test_create_max_pool
will run onlytest_create_max_pool
...
test_create_no_space_loop
will run only
...
test_create_no_space_loop
PoolCreateTests
will run all tests in this class (there is usually one class per file, but in rare cases there are multiple classes per file)
Code Block | ||
---|---|---|
| ||
def test_create_max_pool(self):
"""
:avocado: tags=all,daily_regression
:avocado: tags=hw,medium
:avocado: tags=pool
:avocado: tags=PoolCreateTests,test_create_max_pool
"""
def test_create_no_space_loop(self):
"""
:avocado: tags=all,pr,daily_regression
:avocado: tags=hw,medium
:avocado: tags=pool
:avocado: tags=PoolCreateTests,test_create_no_space_loop
""" |