Skip to content

Support tagging a test as "destructive" #524

@WOnder93

Description

@WOnder93

In the legacy Makefile metadata there used to be a field called Destructive (set to yes or no). Even though I don't know the exact intended meaning, I used it to mark tests that can potentially leave the system in an unusable state (i.e. no further tests can be run without a forced reboot if the bug covered by the test is present). This property is probably quite rare in common testing, but I write mainly kernel tests, where such "destructive" bugs are not that uncommon. I already have two such tests.

So it would be nice if tmt defined a similar attribute in the spec and ideally one day also tried to honor it in some way (e.g. run such tests last, reboot the machine after running them, or even run them on a separate machine if possible).

Metadata

Metadata

Assignees

No one assigned

    Labels

    command | teststmt tests commandspecificationMetadata specification (core, tests, plans, stories)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions