Replies: 1 comment
-
I'm all for better use of these tools. That said, I think the tools can promote behaviours that take us to extremes. For example, I'm not a fan of 100% test coverage as I find this is a deterrent to refactoring. As crazy as that may sound, I am a fan of more black box testing that focuses on APIs and results produced by using those APIs. There are also important but components that should be (mostly) stable that should likely be very heavy guarded with tests. In the case of GCToolkit, this applies to the parsers and I think this focus is demonstrated in the test coverage numbers. That said, I'm all for PRs that adds more/better test coverage. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As above tools already has functionality of showing badges of code coverage , code smells, project maintenance.
Please check the sample links for reference
Ref #50
Beta Was this translation helpful? Give feedback.
All reactions