-
Notifications
You must be signed in to change notification settings - Fork 67
Labels
task:new featureRequesting new capability or software featureRequesting new capability or software featuretheme:core
Description
There is a general mechanism used by Allure integrations to run tests selectively. It uses a testplan - a .json file with the following schema:
{
"type": "object",
"properties": {
"tests": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": { "type": "string" },
"selector": { "type": "string" }
}
}
}
}
}A path to a testplan is provided as a value of the ALLURE_TESTPLAN_PATH environment variable.
If a valid testplan file is provided, only matched tests should be run. A test is matched if there is at least one entry in the tests array, such that:
- It has either the
idproperty, or theselectorproperty or both, AND - If the
idproperty is present in the entry, it must be the same as the Allure ID of the test, AND - If the
selectorproperty is present in the entry, it must be the same as thefullNameof the test.
Motivation
Put allure-csharp integrations in line with other Allure integrations in terms of features.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
task:new featureRequesting new capability or software featureRequesting new capability or software featuretheme:core