You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the mutation score per file is NOT included in the schema but, I presume, calculated on-the-fly by the UI component?
That's problematic because I want to log the score to an external database/chart after stryker4s is finished in CI. Isn't it also duplicating the score calculation in both stryker4s.report.ConsoleReporterand the web UI (and the Dashboard?). 🤔
Any ideas of how I can get the score out into my CI runner would be helpful - short of rendering the UI component in a virtual DOM...
@cbrunnkvist Yes, to prevent duplicate data in the JSON, the mutation score is calculated on the fly.
Rendering the html report definitely doesn't seem ideal, haha. You might want to look at the mutation-testing-elements repo which has a library for Scala and NodeJS to calculate metrics based on a report in a standard way. That code is used by StrykerJS, Stryker4s, the html report and the dashboard to calculate the score (and a couple of other things).
If there's something missing in the metrics, or it doesn't fit your use-case, let me know! We're happy to support more use-cases!
The latest mutation-testing-report-schema release added new properties to the schema. We should fill as many of them as we can:
testFiles
can be filled perfullyQualifiedName
of a test suitecoveredBy
in a mutantkilledBy
in a mutantduration
in a mutanttestsCompleted
in a mutantperformance
framework
, we can filldependencies
with at least the sbt and stryker4s version. Perhaps the test framework toosystem
, we can easily fillci
,os
andcpu
config
The text was updated successfully, but these errors were encountered: