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
Use-case: uncovering and removing un-needed dependencies from large applications
I work on a HUGE application with 50+ gems as dependencies. It's become evident that there are a few gems that were included early on in the project's life that may no longer be necessary or that may be rarely used (maybe one method from it is needed, for example).
The more dependencies there are, the slower the application is when running the tests, starting the app, running rake tasks, starting the console, etc. Finding the least-used gems by using a coverage tool when running the complete suite of specs/cukes would be an ideal way to remedy this problem.
The text was updated successfully, but these errors were encountered:
Yes, this is a reasonable use case and should be possible. I'll look into adding this. For the time being, you could just git clone simplecov into a dir above your project, then specify in your Gemfile for Simplecov:
This will allow you to manipulate simplecov/lib/defaults.rb - comment the adapter loading of root_filter there on line 37. Of course you could also fork and use the git path instead of a local path - that would give you the ability to ditch the if statement in the Gemfile and just always use your forked version of the gem everywhere.
Use-case: uncovering and removing un-needed dependencies from large applications
I work on a HUGE application with 50+ gems as dependencies. It's become evident that there are a few gems that were included early on in the project's life that may no longer be necessary or that may be rarely used (maybe one method from it is needed, for example).
The more dependencies there are, the slower the application is when running the tests, starting the app, running rake tasks, starting the console, etc. Finding the least-used gems by using a coverage tool when running the complete suite of specs/cukes would be an ideal way to remedy this problem.
The text was updated successfully, but these errors were encountered: