Ruby Tests Profiling Toolbox
standard
Ruby Tests Profiling Toolbox | standard | |
---|---|---|
7 | 18 | |
1,793 | 2,596 | |
0.6% | 0.7% | |
7.8 | 8.0 | |
4 days ago | 5 days ago | |
Ruby | Ruby | |
MIT License | GNU General Public License v3.0 or later |
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.
Ruby Tests Profiling Toolbox
-
Must-have gems for mature Rails
gem "test-prof" - https://github.com/test-prof/test-prof | Toolkit for inspecting and optimising your test-suite, a must-have.
-
Measuring load time on fixtures
You might be able to do something with https://test-prof.evilmartians.io, but I'm not sure it has anything specific to fixtures out of the box. Maybe using the event profiler on sql.active_record events would be close enough. In the limit, you could wire together your own ActiveSupport::Notifications.instrument around the relevant blocks + an ActiveSupport::Notifications.subscribe to that event so as to log the relevant information. Docs: https://api.rubyonrails.org/classes/ActiveSupport/Notifications.html
-
How to optimize factory creation.
To have a better vision of what objects are created in our spec file we can use test-prof, a powerful gem that provides a collection of different tools to analyse your test suite performance. One of this tool is really useful to identify a factory cascade, let’s introduce factory profiler.
-
A Trick For Reading Flamegraphs
TestProf can be used to get flamegraphs for Ruby test suites.
- How to improve a test suit made with Rspec, Capybara, FactoryBot and Siteprism
-
Does pytest break a lot of coding rules?
Rspec has spec_helper.rb.
-
Learning resources to broaden the knowledge
I also love the test-prof documentation, there's a lot of good ideas on how to improve test performance.
standard
-
Am I the only one who doesn't put parentheses around the parameters in Ruby method definitions?
Rubocop has a default rule that says to put parentheses when there are parameters; even Standardrb has a default ([https://github.com/standardrb/standard/blob/8307fa8f449f896075ccad 74bf6a128ed2c26189/config/base.yml#L1098:title])
- Standardrb: Ruby's bikeshed-proof linter and formatter
-
Must-have gems for mature Rails
gem "rubocop" - https://github.com/rubocop/rubocop | Set up code guidelines for your dev team, I recommend using whatever Standard recommends.
-
A Writer's Ruby
Cynically, reading heavily between the lines, this reads to me like DHH just found out lots of rubyists like standardrb. https://github.com/standardrb/standard -- and this is his quick reaction to it.
-
"Useless Ruby sugar": Endless (one-line) methods
This is a huge reason why I still use StandardJS and—shifting back to Ruby—why I rejected the countless requests for implementing line-length or any other metrics analysis rules for [StandardRB](https://github.com/standardrb/standard). There is always a legitimate edge case when it comes to length of lines and functions and the alternative—chopping them off arbitrarily—is rarely an improvement.
-
An Introduction to RuboCop for Ruby on Rails
This approach is known as Standard Ruby. It can also be completed with plugins, including one for Ruby on Rails projects.
-
It's Official: the Standard Ruby VS Code extension
Oh, this is fantastic! Would you be willing to send a quick PR to our README?
-
Rails vs Rubocop?
[0] https://github.com/testdouble/standard
-
Linting and Auto-formatting Ruby Code With RuboCop
If you don't want to fiddle with configuration files and the wealth of options provided by RuboCop, consider taking a look at the Standard project. It's largely a pre-configured version of RuboCop that aims to enforce a consistent style in your Ruby project without allowing the customization of any of its rules. The lightning talk where it was first announced gives more details about its origin and motivations.
- Utilizando o padrĂŁo interactor no Ruby on Rails
What are some alternatives?
DuckRails - Development tool to mock API endpoints quickly and easily (docker image available)
Ruby style guide - A community-driven Ruby coding style guide
Spinach - Spinach is a BDD framework on top of Gherkin.
eslint-config-standard - ESLint Config for JavaScript Standard Style
minitest - minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking.
rubocop-rspec - Code style checking for RSpec files
timecop - A gem providing "time travel", "time freezing", and "time acceleration" capabilities, making it simple to test time-dependent code. It provides a unified method to mock Time.now, Date.today, and DateTime.now in a single call.
ansi-strikethrough - The color strikethrough, in ansi.
factory_bot - A library for setting up Ruby objects as test data.
rubocop-rails - A RuboCop extension focused on enforcing Rails best practices and coding conventions.
faker - A library for generating fake data such as names, addresses, and phone numbers.
Hanami::Model - Ruby persistence framework with entities and repositories