Skip to content

Make it possible to describe test environment and conditions in the test itself #234

Open
@Gerold103

Description

@Gerold103

Some tests should be run only in debug, some may run multiple times with different engines, some may not run on certain OSs. Currently control over this is spread over suite.ini, suite.cfg, and .skipcond files. And it is getting harder. Just look at suite.ini and suite.cfg file of a big suite like replication. The release_disabled is already huge. Suite.cfg automatically runs all tests not listed as exceptions with 2 engines, even though it often is not needed, and a test not added there by accident.

It would be much easier, if a test itself could decide if it can run in the current environment, and how many times with which arguments.

The issue becomes more actual with the new policy of having a testfile-per-bug. Number of the files becomes enormous.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureA new functionality

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions