turbo_tests
Parallel Tests
turbo_tests | Parallel Tests | |
---|---|---|
1 | 6 | |
155 | 3,342 | |
0.6% | - | |
5.2 | 7.6 | |
15 days ago | 6 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.
turbo_tests
Parallel Tests
-
Seeking help with moving a locally running, short-lived Docker container to CI / deployment process?
Thanks for that feedback. For some more context, the container is designed to run 40+ processes in parallel sending remote instructions to AWS Device Farm for testing, so I suspect that the RAM usage is expected in this case. If you have any recommendations on re-architecting the execution here I'm all ears.
- working with factory bot and active storage
- How to improve a test suit made with Rspec, Capybara, FactoryBot and Siteprism
-
Who's using Rails 7 test
I know changing from RSpec to MiniTest requires some changes on how you organize the tests and how you think about writing them, but I found that I like MiniTest better after using it for more time, I think it goes straight to the point and it's better integrated (don't quote me on this, but I think minitest handles parallel tests better than RSpec in Rails app because that feature was added with mini test in mind, you would need to add an extra gem for rspec for that https://github.com/grosser/parallel_tests)
-
How We Sped up Our CI Pipeline by Over 4x
Several members of our team worked together to get the parallel_tests gem working for our codebase. Most of our tests were fine running in parallel, but we found enough that made assumptions about the order they would be run in that we had to do some fixing and rewriting. We kept this work in a feature branch, and kept chipping away at it until all the tests would pass.
-
The Perils of Parallel Testing in Ruby on Rails
Let's get one thing out of the way. If you use RSpec rather than Minitest, you are out of luck. RSpec does not support Rails 6 built-in parallel testing. There is an ongoing discussion about changing that, but there hasn't been any significant progress for a while. If you want parallel tests with RSpec, your best bet is still using third-party gems such as grosser/parallel_tests.
What are some alternatives?
RSpec - RSpec meta-gem that depends on the other components
Knapsack - Knapsack splits tests evenly across parallel CI nodes to run fast CI build and save you time.
Capybara - Acceptance test framework for web applications
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.
factory_bot - A library for setting up Ruby objects as test data.
vcr - Record your test suite's HTTP interactions and replay them during future test runs for fast, deterministic, accurate tests.
WebMock - Library for stubbing and setting expectations on HTTP requests in Ruby.
Spring - Rails application preloader
Ruby-JMeter - A Ruby based DSL for building JMeter test plans
DuckRails - Development tool to mock API endpoints quickly and easily (docker image available)
mutant - Automated code reviews via mutation testing - semantic code coverage.