Add option to mark integration tests CTAO use case and requirements.

[GernotMaier]

Allow to mark integration tests in their use case config with a corresponding CTAO use case or requirement ID, see pytest-requirements package description.

• adds additional dependency pytest-requirements](http://cta-computing.gitlab-pages.cta-observatory.org/common/pytest-requirements/latest/quickstart.html)
• adds two new keywords to the application_workflow.metaschema: TEST_REQUIREMENT and TEST_USE_CASE
• small additions to test_applications_from_config to mark the tests.
• added only to one single test for now a TEST_USE_CASE marker (this PR is about adding the functionality; so don't worry that this is a random use case ID).

[ctao-dpps-sonarqube]

Analysis Details

0 Issues

• 0 Bugs
• 0 Vulnerabilities
• 0 Code Smells

Coverage and Duplications

• No coverage information (94.30% Estimated after merge)
• 0.00% Duplicated Code (0.00% Estimated after merge)

Project ID: gammasim_simtools_AY_ssha9WiFxsX-2oy_w

View in SonarQube

[maxnoe]

A minor note, as I don't know if this is relevant to you, in general, the use case to test mapping is many-to-many.

So you might want to make the id fields lists instead of a single string and add a loop to add the markers.

[GernotMaier]

@maxnoe - thanks for this. This will be easy to extend - I however can't think a case right now where this would be the case. I suggest to review this PR and add the extension to list when needed.

[tobiaskleiner]

Maybe consider adding a short docstring.