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
To get the best results, make sure that you have coverage/.resultset.json in
your application directory. That way skunk knows what's the status of your
test suite + code coverage.
Running skunk without that file is kind of pointless. The whole idea of the "StinkScore" is to combine RubyCritic's cost with SimpleCov's lack of coverage, in order to get a realistic "StinkScore"
So we should make sure the user understands that the scores that they're getting is not that useful.
The text was updated successfully, but these errors were encountered:
@bronzdoc I don't think we should make it a requirement, I think it should output a noticeable warning. We have to assume that sometimes a project has no test suite, so they won't have code coverage data, but as they add coverage to their codebase, they might want to see the evolution of their stink score average (related to #5)
In the README.md:
Running
skunk
without that file is kind of pointless. The whole idea of the "StinkScore" is to combine RubyCritic's cost with SimpleCov's lack of coverage, in order to get a realistic "StinkScore"So we should make sure the user understands that the scores that they're getting is not that useful.
The text was updated successfully, but these errors were encountered: