Sometimes it is required to logically group together tests that are expected to be executed in certain OSP environment (see infrared here).

• How are we going to deal with grouping of these tests in OSP18?
  • tempest-skiplist
• Do we need to group the tests similarly as we did in OSP17 and lower? 
  • not necessarily as it depends on the jobs we (will) have and the fact that we should follow ci-framework for consistency, thus tempest-skiplist

We will use  list_allowed.yml  and list_skipped.yml in the test-operator role. The tempest role uses those like this - we can implement it analogically (and test-operator role uses those already like this).

NOTE: keep in mind that the allowed and skipped lists should be maintained by different teams/DFGs/job owners/maintainers. Thus the lists should live somewhere where those teams can maintain them themselves .. in other words, edit of the lists should not require a PR on the test-operator role.

DoD:

• test-operator role in ci-framework uses tempest-skiplist
• users can run different set of tempest tests using the test-operator role in ci-framework - e.g. a user has 2 test sets and the tests from the set 1 can't be executed together with the tests from the set 2