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
What is your use-case and why do you need this feature?
In some cases, it is necessary to perform additional actions after measuring the coverage: for example, perform conditional verification, write values to the log, write the coverage values to the file in any form.
Kover cannot provide for all use cases.
However, we can provide a factory with which users can create tasks that perform coverage processing
Describe the solution you'd like
kover {
reports {
total {
evaluations.create("myLog") {
// use build caching
isCacheable =false// action to execute
action {
logger.info("Total coverage: ${lines.coveredPercentage}%")
}
// a way to get a task to specify future dependencies
taskProvider
}
}
}
}
I was just looking for something like this. Similar to #545, I need slightly more advanced verification logic:
pseudocode
if (numberOfBranches >50&& branchesCoveredPercent <1) {
failVerfication()
}
Just like #545, I have some very small modules failing verifications because in shared build logic I make it so all modules have to cover at bare minimum 1 percent of branches. I've had cases where a module has less than 10 branches and this is not ideal for me to fail verification in this case.
What is your use-case and why do you need this feature?
In some cases, it is necessary to perform additional actions after measuring the coverage: for example, perform conditional verification, write values to the log, write the coverage values to the file in any form.
Kover cannot provide for all use cases.
However, we can provide a factory with which users can create tasks that perform coverage processing
Describe the solution you'd like
and later executed via
koverMyLogAction
Use cases: #545 and #419
The text was updated successfully, but these errors were encountered: