Skip to content

Define some common test plans that run all features #4576

@LecrisUT

Description

@LecrisUT

Extracted from #4208. Basically we are starting to redefine again and again some test plans that do the same thing: run a basic plan with all features enabled and verified. So it would be good to consolidate much of those.

Basically we can have two commonly used plans minimal and full, which run the minimum features (discover+execute) or all features (dependencies, libraries, etc.). This can be reused when we want to test against different provision types, or with minor adjustments to them. This would not change the specific plans that test various types of discover plugins, but can serve as the baseline from where to expand from.

If we move these to pytest, then we will get the added benefit of being able to run these only once and use the tests to verify various aspects of the run.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area | maintenanceChanges important for efficiency and the long-term health of the projecttest coverageImprovements or additions to test coverage of tmt itself

    Type

    Projects

    Status

    waiting

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions