retest VS Puma

Whatever you choose Retest (a gem I maintain) will acknowledge both naming conventions out of the box to increase the number of compatible Ruby projects. This is done in release 1.10.0. For example, you can now use Retest with Puma.

I created a gem: Retest which works on the terminal. A bit like Guard without any setup. The gem is smart enough to find the correct file to test after you save any.rb file.

I use retest. It works on every standard Ruby projects with no setup (understand no .Guardfile or Gemfile update). If you follow rspec, rails, rake or ruby standard file structure you get running in less than a minute. As a contractor I can checkout any repo and start TDD without caring about the repo setup. I use it even when Guard is already installed because the experience is consistent across all projects. It also has a —diff option that runs only spec files relevant from the diffs with another branch to run a final check before creating a pull request and triggering the whole test suite on CI.

But whatever the project I’m working on is, I always try using retest https://github.com/AlexB52/retest for awesome refactoring and TDD because it works with both Minitest and RSpec out of the box. Sorry for the shameless promotion.

Hi, I have created a gem called retest that helps you run specs after a file change without adding any configuration files to a repo. I created it for the specific reason you’re mentioning as I work in a consultancy. It is supposed to be dev centric and works with any ruby projects. I use it while working or refactoring. It might suits you, have a look

A great book by Sandi Metz is 99 bottles of OOP in Ruby where she explains heaps about refactoring. One of the best book I have read. I know you asked for article or videos but if you have time, it takes a day or two to read. I made a gem to help people refactor the same way she describes in the book. It will speed up your feedback loop when refactoring: retest

As we use Puma as our webserver for our rails application, I quickly went to Puma's config file which typically resides in config/puma.rb. The config was set as

They do! It's in the first section of the readme on the repo:

Start with service with systemd

# Use the Puma web server [https://github.com/puma/puma] gem "puma", "~> 5.0" # Build JSON APIs with ease [https://github.com/rails/jbuilder] # gem "jbuilder" gem 'rack-cors' gem "devise" gem "jsonapi-serializer" gem 'devise-jwt' gem 'active_model_serializers' gem 'followability' gem 'dotenv-rails', groups: [:development, :test, :production] gem 'sprockets' # Use Redis adapter to run Action Cable in production # gem "redis", "~> 4.0" # Use Kredis to get higher-level data types in Redis [https://github.com/rails/kredis] # gem "kredis" # Use Active Model has_secure_password [https://guides.rubyonrails.org/active_model_basics.html#securepassword] # gem "bcrypt", "~> 3.1.7" # Windows does not include zoneinfo files, so bundle the tzinfo-data gem gem "tzinfo-data", platforms: %i[ mingw mswin x64_mingw jruby ] # Reduces boot times through caching; required in config/boot.rb gem "bootsnap", require: false # Use Active Storage variants [https://guides.rubyonrails.org/active_storage_overview.html#transforming-images] # gem "image_processing", "~> 1.2" # Use Rack CORS for handling Cross-Origin Resource Sharing (CORS), making cross-origin AJAX possible # gem "rack-cors" group :development, :test do # See https://guides.rubyonrails.org/debugging_rails_applications.html#debugging-with-the-debug-gem gem "debug", platforms: %i[ mri mingw x64_mingw ] end group :development do gem "sqlite3", "~> 1.4" # Speed up commands on slow machines / big apps [https://github.com/rails/spring] # gem "spring" end group :production do gem 'pg' end

source "https://rubygems.org" git_source(:github) { |repo| "https://github.com/#{repo}.git" } ruby "3.1.0" # Bundle edge Rails instead: gem "rails", github: "rails/rails", branch: "main" gem "rails", "~> 7.0.4", ">= 7.0.4.2" # The original asset pipeline for Rails [https://github.com/rails/sprockets-rails] gem "sprockets-rails" # Use sqlite3 as the database for Active Record gem "sqlite3", "~> 1.4" # Use the Puma web server [https://github.com/puma/puma] gem "puma", "~> 5.0" # Use JavaScript with ESM import maps [https://github.com/rails/importmap-rails] gem "importmap-rails" # Hotwire's SPA-like page accelerator [https://turbo.hotwired.dev] gem "turbo-rails" # Hotwire's modest JavaScript framework [https://stimulus.hotwired.dev] gem "stimulus-rails" # Build JSON APIs with ease [https://github.com/rails/jbuilder] gem "jbuilder" gem "mongoid" gem "mongoid-grid_fs" gem 'bootstrap', '~> 5.2.2' #sourced from https://github.com/twbs/bootstrap-rubygem gem 'rack-cors' # Windows does not include zoneinfo files, so bundle the tzinfo-data gem gem "tzinfo-data", platforms: %i[ mingw mswin x64_mingw jruby ] # Reduces boot times through caching; required in config/boot.rb gem "bootsnap", require: false

That doesn't mean one excludes the other. Gems like Puma use the instance_eval method for their configuration file.

Anyway I did it: https://github.com/puma/puma/issues/3003 It's quite more complicated: https://github.com/puma/puma/issues/2999 A fix is in progress: https://github.com/puma/puma/pull/3002