Commit
* Replace `badge` logger with more advanced `stryker` logger Related to #1625 Now, Stryker logger allows to send badge information or the full mutation test elements report to display HTML report on Stryker Dashboard. Example: https://dashboard.stryker-mutator.io/reports/github.com/infection/infection/master#mutant Note, at the time of creating this PR, Stryker Dashboard has an old version of mutation-testing-elements lib which is too slow. Made a PR to update it: stryker-mutator/stryker-dashboard#211. The locally generated `html` report (see `logger.html` in `infection.json` already generates report with the latest lib) This is a BC break. Before: `infection.json` ```json { "logs": { "badge": { "branch": "master" } } } ``` After: `infection.json` - for badge information only ```json { "logs": { "stryker": { "badge": "master" } } } ``` or for badge *and* HTML report ```json { "logs": { "badge": { "report": "master" } } } ``` * Add more tests, remove todo
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,8 +7,8 @@ | |
] | ||
}, | ||
"logs": { | ||
"badge": { | ||
"branch": "master" | ||
"stryker": { | ||
"badge": "master" | ||
} | ||
}, | ||
"mutators": { | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -70,26 +70,27 @@ | |
"type": "string", | ||
"description": "Markdown file which will give a break-down of the effectiveness of each mutator." | ||
}, | ||
"badge": { | ||
"type": "object", | ||
"description": "Mutation score badge for your GitHub project. If provided, infection will report results for maching branches to an upstream reporting dashboard/collector.", | ||
"additionalProperties": false, | ||
"required": ["branch"], | ||
"properties": { | ||
"branch": { | ||
"type": "string", | ||
"description": "Mutation score badge for your GitHub project. If this value starts and ends with \"/\", it will be considered a regular expression.", | ||
"exaples": [ | ||
"main", | ||
"master", | ||
"develop", | ||
"latest", | ||
"/1\\.\\d+/", | ||
"/release-.*/", | ||
"/feature\\/.*/" | ||
] | ||
"stryker": { | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
maks-rafalko
Author
Member
|
||
"oneOf": [ | ||
This comment has been minimized.
Sorry, something went wrong.
Ocramius
Contributor
|
||
{ | ||
"type": "object", | ||
"required": ["badge"], | ||
"description": "Mutation score badge for your GitHub project. If provided, Infection will report results for matching branches to an upstream reporting dashboard.", | ||
"additionalProperties": false, | ||
"properties": { | ||
"badge": { "$ref": "#/definitions/stryker-branch" } | ||
} | ||
}, | ||
{ | ||
"type": "object", | ||
"required": ["report"], | ||
"description": "Mutation score badge for your GitHub project. If provided, Infection will report results for matching branches to an upstream reporting dashboard.", | ||
"additionalProperties": false, | ||
"properties": { | ||
"report": { "$ref": "#/definitions/stryker-branch" } | ||
} | ||
} | ||
} | ||
] | ||
}, | ||
"github": { | ||
"type": "boolean", | ||
|
@@ -603,6 +604,19 @@ | |
} | ||
} | ||
] | ||
}, | ||
"stryker-branch": { | ||
"type": "string", | ||
"description": "Mutation score badge for your GitHub project. If this value starts and ends with \"/\", it will be considered a regular expression.", | ||
"examples": [ | ||
"main", | ||
"master", | ||
"develop", | ||
"latest", | ||
"/1\\.\\d+/", | ||
"/release-.*/", | ||
"/feature\\/.*/" | ||
] | ||
} | ||
} | ||
} |
The fact that
"badge"
no longer exists at top-level is a bit of an annoying BC break: is this intentional?