🚀 TurboTests

if ci_badges.map(&:color).detect { it != "green"} ☝️ let me know, as I may have missed the discord notification.

if ci_badges.map(&:color).all? { it == "green"} 👇️ send money so I can do more of this. FLOSS maintenance is now my full-time job.

I've summarized my thoughts in this blog post.

turbo_tests2 is a drop-in replacement for, and modernization of, turbo_tests, which is a drop-in replacement for grosser/parallel_tests, adding incremental summarized output. Source code of this gem is based on Discourse and RubyGems work in this area.

Incremental summarized output doesn't fit vision of parallel_tests author and RSpec doesn't support built-in parallel testing yet. This gem will not be useful once one of the issues above will be implemented.

parallel_tests is great, but it messes output:

$ bundle exec rake parallel_tests:spec[^spec/search]
.................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Finished in 1 minute 6.92 seconds (files took 6.95 seconds to load)
2616 examples, 0 failures

.........................................................................................................................................F........................................................................................................................................F..............................................................................................................................................................................................................................................................................................

Finished in 1 minute 35.05 seconds (files took 6.26 seconds to load)
2158 examples, 2 failures

.................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Finished in 1 minute 35.05 seconds (files took 6.26 seconds to load)
2158 examples, 0 failures

turbo_tests2 output looks like regular rspec:

$ bundle exec turbo_tests2
..........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................F........................................................................................................................................F..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Finished in 2 minute 25.15 seconds (files took 0 seconds to load)
6873 examples, 2 failures

Tokens to Remember
Works with JRuby
Works with Truffle Ruby
Works with MRI Ruby 4
Works with MRI Ruby 3
Works with MRI Ruby 2
Support & Community
Source
Documentation
Compliance
Style
Maintainer 🎖️
... 💖	🧊 🐙 🛖 🧪

Compatible with MRI Ruby 2.4.0+, and concordant releases of JRuby, and TruffleRuby. CI workflows and Appraisals are generated for MRI Ruby 2.4+. This test floor is configured by ruby.test_minimum in .kettle-jem.yml and may be higher than the gem's runtime compatibility floor when legacy Rubies are not practical for the current toolchain.

Federated DVCS Repository	Status	Issues	PRs	Wiki	CI	Discussions
🧪 galtzo-floss/turbo_tests2 on GitLab	The Truth	💚	💚	💚	🐭 Tiny Matrix	➖
🧊 galtzo-floss/turbo_tests2 on CodeBerg	An Ethical Mirror (Donate)	💚	💚	➖	⭕️ No Matrix	➖
🐙 galtzo-floss/turbo_tests2 on GitHub	Another Mirror	💚	💚	💚	💯 Full Matrix	💚
🎮️ Discord Server		Let's	talk	about	this	library!

Available as part of the Tidelift Subscription.

The maintainers of this and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source packages you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact packages you use.

• 💡Subscribe for support guarantees covering all your FLOSS dependencies
• 💡Tidelift is part of Sonar
• 💡Tidelift pays maintainers to maintain the software you depend on!
  📊@Pointy Haired Boss: An enterprise support subscription is "never gonna let you down", and supports open source maintainers

Alternatively:

Install the gem and add to the application's Gemfile by executing:

bundle add turbo_tests2

If bundler is not being used to manage dependencies, install the gem by executing:

gem install turbo_tests2

turbo_tests2 ships the turbo_tests2 executable by default.

If you want an opt-in compatibility command for a specific project, generate a local shim:

$ bundle exec turbo_tests2 shim install
Installed turbo_tests shim at bin/turbo_tests.

That creates bin/turbo_tests, which delegates to bundle exec turbo_tests2 "$@". Remove it with:

$ bundle exec turbo_tests2 shim remove
Removed turbo_tests shim at bin/turbo_tests.

Create test databases

$ bundle exec turbo_tests2 --create

Show help:

$ bundle exec turbo_tests2 -h
Usage: turbo_tests2 [options]

[optional] Only selected files & folders:
  turbo_tests2 spec/bar spec/baz/xxx_spec.rb

Options:
    -n [PROCESSES]                   How many processes to use, default: available CPUs
    -r, --require PATH               Require a file.
    -f, --format FORMATTER           Choose a formatter. Available formatters: progress (p), documentation (d). Default: progress
    -t, --tag TAG                    Run examples with the specified tag.
    -o, --out FILE                   Write output to a file instead of $stdout
        --runtime-log FILE           Location of previously recorded test runtimes
    -v, --verbose                    More output
        --fail-fast=[N]
        --seed SEED                  Seed for rspec
        --create                     Create test databases
        --print_failed_group         Prints group that had failures in it

To pass any options supported by paralell_tests, use --:

bundle exec turbo_tests2 -n 4 -- --only-group 1 --pattern spec/system

turbo_tests2 supports custom formatter such as Fuubar, but you might need to require it:

bundle exec turbo_tests2 -r fuubar -f Fuubar spec/whatever

If Rake is present, the CLI will invoke the tasks turbo_tests:setup and turbo_tests:cleanup before and after running the test suite. These can be used to do work that should only happen once, such as removing files or collating coverage:

# lib/tasks/turbo_tests.rake
namespace :turbo_tests do
  task setup: :environment do
    # precompile assets once, to avoid doing it per each process
    Rake::Tasks["assets:precompile"]
  end

  task cleanup: :environment do
    # keep things nice and tidy
    Rake::Tasks["assets:clobber"]
  end
end

You can get accurate coverage reporting by having SimpleCov write the results for each process into a different directory and then have the results collated as part of cleanup:

# spec/spec_helper.rb
require "simplecov"

# Configure minimum test coverage levels
#
# Details of default values for these configuration options can be seen at
# https://github.com/simplecov-ruby/simplecov/blob/master/lib/simplecov/profiles/rails.rb
SimpleCov.start("rails") do
  enable_coverage :branch

  coverage_dir "coverage/turbo_tests/#{ENV["TEST_ENV_NUMBER"]}"

  formatter SimpleCov::Formatter::SimpleFormatter
end

# lib/tasks/turbo_tests.rake
namespace :turbo_tests do
  task setup: :environment do
    # remove any existing coverage files to avoid false reporting
    FileUtils.rm_rf("coverage/turbo_tests")
  end

  task cleanup: :environment do
    require "simplecov"

    # report coverage usage based on the results of all tests
    SimpleCov.collate(Dir["coverage/turbo_tests/*/.resultset.json"]) do
      enable_coverage :branch

      minimum_coverage line: 100, branch: 100
    end
  end
end

While galtzo-floss tools are free software and will always be, the project would benefit immensely from some funding. Raising a monthly budget of... "dollars" would make the project more sustainable.

We welcome both individual and corporate sponsors! We also offer a wide array of funding channels to account for your preferences. Currently, Open Collective is our preferred funding platform.

If you're working in a company that's making significant use of galtzo-floss tools we'd appreciate it if you suggest to your company to become a galtzo-floss sponsor.

You can support the development of galtzo-floss tools via GitHub Sponsors, Liberapay, PayPal, Open Collective and Tidelift.

Support us with a monthly donation and help us continue our activities. [Become a backer]

NOTE: kettle-readme-backers updates this list every day, automatically.

No backers yet. Be the first!

Become a sponsor and get your logo on our README on GitHub with a link to your site. [Become a sponsor]

NOTE: kettle-readme-backers updates this list every day, automatically.

No sponsors yet. Be the first!

I’m driven by a passion to foster a thriving open-source community – a space where people can tackle complex problems, no matter how small. Revitalizing libraries that have fallen into disrepair, and building new libraries focused on solving real-world challenges, are my passions. I was recently affected by layoffs, and the tech jobs market is unwelcoming. I’m reaching out here because your support would significantly aid my efforts to provide for my family, and my farm (11 🐔 chickens, 2 🐶 dogs, 3 🐰 rabbits, 8 🐈‍ cats).

If you work at a company that uses my work, please encourage them to support me as a corporate sponsor. My work on gems you use might show up in bundle fund.

I’m developing a new library, floss_funding, designed to empower open-source developers like myself to get paid for the work we do, in a sustainable way. Please give it a look.

Floss-Funding.dev: 👉️ No network calls. 👉️ No tracking. 👉️ No oversight. 👉️ Minimal crypto hashing. 💡 Easily disabled nags

See SECURITY.md.

If you need some ideas of where to help, you could work on adding more code coverage, or if it is already 💯 (see below) check issues or PRs, or use the gem and think about how it could be better.

We so if you make changes, remember to update it.

See CONTRIBUTING.md for more detailed instructions.

See CONTRIBUTING.md.

Everyone interacting with this project's codebases, issue trackers, chat rooms and mailing lists agrees to follow the .

Made with contributors-img.

Also see GitLab Contributors: https://gitlab.com/galtzo-floss/turbo_tests2/-/graphs/main

This library follows for its public API where practical. For most applications, prefer the Pessimistic Version Constraint with two digits of precision.

For example:

spec.add_dependency("turbo_tests2", "~> 3.0")

Dropping support for a platform can be a breaking change for affected users. If a release changes supported platforms, it should be called out clearly in the changelog and versioned with that impact in mind.

To get a better understanding of how SemVer is intended to work over a project's lifetime, read this article from the creator of SemVer:

• "Major Version Numbers are Not Sacred"

See CHANGELOG.md for a list of releases.

The gem is available as open source under the terms of the MIT .

See LICENSE.md for the official copyright notice.

• Copyright (c) 2020-2023 Illia
• Copyright (c) 2020 Ilya Zub
• Copyright (c) 2021 AMHOL
• Copyright (c) 2021 Serge Bedzhyk
• Copyright (c) 2023 Bo Anderson
• Copyright (c) 2023 Dmitiry Zub☀️
• Copyright (c) 2023-2024 Illia
• Copyright (c) 2023 mrudzki
• Copyright (c) 2023-2024 Sebastien Savater
• Copyright (c) 2024 David Rodriguez
• Copyright (c) 2024 Hiroshi SHIBATA
• Copyright (c) 2025 Gareth Jones
• Copyright (c) 2025-2026 Peter H. Boling

Maintainers have teeth and need to pay their dentists. After getting laid off in an RIF in March, and encountering difficulty finding a new one, I began spending most of my time building open source tools. I'm hoping to be able to pay for my kids' health insurance this month, so if you value the work I am doing, I need your support. Please consider sponsoring me or the project.

To join the community or get help 👇️ Join the Discord.

To say "thanks!" ☝️ Join the Discord or 👇️ send money.

💌 💌 💌

Thanks for RTFM. ☺️