SimpleCov
packwerk
SimpleCov | packwerk | |
---|---|---|
11 | 16 | |
4,708 | 1,500 | |
0.1% | 2.1% | |
6.6 | 7.0 | |
5 days ago | 5 days ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SimpleCov
-
Must-have gems for mature Rails
gem "simplecov" - https://github.com/simplecov-ruby/simplecov | Gather spec coverage stats locally and on CI, aim for those 90+%.
-
Evaluating More Coverage in Ruby 3.2
Have you wondered how much of the logic in your views is exercised in your test suite? Thanks to this change, now you can see that in tools like SimpleCov.
-
My First Code Commit in Ruby
My talk is about different best practices - specifically when adhering to them breaks down. One of those best practices is high test coverage. I start to work on the content for my presentation by building the code samples that I want to use in the slides. For the code coverage section, I'm writing some code with some tests. I'm using SimpleCov to generate code coverage results.
- Falha de cobertura: Divagações sobre testes de software
-
Improve Code in Your Ruby Application with RubyCritic
SimpleCov - a tool to check Ruby application code coverage. You can configure it to run alongside your tests. It provides metrics on code coverage so that you can identify what you need to pay attention to and where to invest your time to create better test cases.
-
Paying Down Technical Debt
Ensure that you have sufficient test coverage. You can use code coverage analysis tools like SimpleCov to gain insight into gaps in your coverage.
-
How to test all workers in one big loop?
simplecov might the answer you need, it generates a report of the lines of code your test suite hits.
-
How to Improve Code Quality on a Ruby on Rails Application
Use SimpleCov to generate a report of how many statements are covered by your test suite. It won't assess the test suite quality, though.
-
Ruby's Got You Covered
There are many tools for measuring test coverage, but one is SimpleCov. It also supports branches coverage. To measure coverage of production code, check out Coverband, which you can set up to use oneshot lines mode.
- Como configurar ambiente de testes em Ruby on Rails com RSpec
packwerk
-
Must-have gems for mature Rails
gem "packwerk" - https://github.com/Shopify/packwerk | Allows modularising Ruby code, a must-have for growing projects.
-
Keep the Monolith, but Split the Workloads
Yep, that article is about very similar concepts but grounded in Spring as the framework.
I like what they do around package imports and it looks a lot like what we do at incident.io, with some rules about which packages can import what.
For people in the Ruby world who want a similar solution, Shopify provide an open-source framework called packwerk that is designed just for this:
https://github.com/Shopify/packwerk
-
All you need is Rails (Engines): Compartmentalising your Monolith
I’d probably go with packwerk before rails engines these days
-
How to break up a rails monolith
https://github.com/Shopify/packwerk allows you to make dependencies between components explicit
- Best way to go about fragmenting a Monolithic Rails application into Microservices.
-
OOP vs. services for organizing business logic: is there a third way?
Packwerk – to enforce boundaries and modularize Rails applications
-
Organizing Rails files by meaning
Take a look at Packwerk from some folks at Shopify - gets you the benefits of naming some components for organizing boundaries in your code, with each component having the usual rails folder structure, but without the hard isolation restrictions of doing so with Engines.
-
How to edit a model from another controller
Nothing is stopping you from doing so except you (and maybe packwerk, but you very likely don't have that installed).
-
The advent of tooling for Big Rails
For me, the most important aspect of a growing Rails app is handling of complexity and interdependencies and turns out Shopify's packwerk is just what the doctor ordered - it leverages zeitwerk loader to improve on Rails' vanilla file structure, allowing to group files by business concept or sub-domain and control visibility and ownership.
-
Exploring DryRB - Intuition of Results
Let's set the stage right quick. You happen to be in a large Rails application that follows along with something like Packwerk to clearly delineate different packages in your Rails monolith. Let's say you have 100 packs, which is not particularly unusual with larger applications.
What are some alternatives?
Coverband - Ruby production code coverage collection and reporting (line of code usage)
Solidus - 🛒 Solidus, the open-source eCommerce framework for industry trailblazers.
Rubocop - A Ruby static code analyzer and formatter, based on the community Ruby style guide. [Moved to: https://github.com/rubocop/rubocop]
appmap-ruby - AppMap client agent for Ruby
Rubycritic - A Ruby code quality reporter
django-rq - A simple app that provides django integration for RQ (Redis Queue)
undercover - undercover warns about methods, classes and blocks that were changed without tests, to help you easily find untested code and reduce the number of bugs. It does so by analysing data from git diffs, code structure and SimpleCov coverage reports
whitehall - Publishes government content on GOV.UK
Pronto - Quick automated code review of your changes
suture - 🏥 A Ruby gem that helps you refactor your legacy code
rails_best_practices - a code metric tool for rails projects
gitlab