You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When multiple phase are used in the discover step, phase name is presented as a part of the test name. Filtering, however, does support only the real test name, without the prefix.
Example of a discover step defining two named phases which import tests from a remote url:
discover:
- name: first
url: ...
...
- name: second
url: ...
...
Both destinations could contain tests named /tests/one and /tests/two, and currently, tmt presents the discovered tests including the phase name:
Currently, it is not possible to filter by the names as they're presented, running tmt run discover test --name /first/tests/one would not return anything as the test name is actually just /tests/one.
As discussed, the phase name should be distinguished from the test name:
When multiple phase are used in the discover step, phase name is presented as a part of the test name. Filtering, however, does support only the real test name, without the prefix.
Example of a discover step defining two named phases which import tests from a remote url:
Both destinations could contain tests named
/tests/one
and/tests/two
, and currently, tmt presents the discovered tests including the phase name:Currently, it is not possible to filter by the names as they're presented, running
tmt run discover test --name /first/tests/one
would not return anything as the test name is actually just/tests/one
.As discussed, the phase name should be distinguished from the test name:
On the command line, using the phase name will be allowed when filtering tests by name:
Additinonally, the discover phase name should be stored in the tests.yaml (already) and results.yaml (tbd).
Encountered in https://redhat-internal.slack.com/archives/C03BRN71JAF/p1708424104910169.
The text was updated successfully, but these errors were encountered: