retest VS minitest

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

In this part, we’ll set up our testing environment so that we can test our Rails API using minitest with minitest/spec. We’ll look at the differences between traditional style unit tests and spec-style tests, or specs. I’ll demonstrate why you should use minitest-rails. We’ll look at using rack-test for testing our API. We’ll even create our own generator to generate API specs.

I forgot to mention that reading code is also a good way to learn how to write code, it's like inspiration. Check repos of some gems you like. For example sidekiq https://github.com/sidekiq/sidekiq/tree/main/lib/sidekiq Or minitest https://github.com/minitest/minitest/tree/master/lib/minitest

All through GitHub.

1. From https://github.com/rails/rails/blob/6ffb29d24e05abbd9ffe3ea9..., click "Blame" on the header bar over the file contents.

2. Scroll down to the line and click on the commit in the left column.

3. Scroll down to the file that removed the line from its previous file, activesupport/lib/active_support/test_case.rb.

4. Click the three-dots menu in that file's header bar and select "View file".

5. Click "History" in the header bar of the contributors, above the file contents.

6. I guessed here at commit 281f488 on its message: "Use the method provided by minitest to make tests order dependent". There's a comment here that identified the problem which led to, and provided context for, the change in 6ffb29d.

The OP is from minitest's documentation, so to find the introduction in minitest, it's basically the same process.

1. Go to https://github.com/minitest/minitest.

2. Search the repo for the method name. Even just "i_suck" will match the commit.

3. Select the oldest commit in the results. That's a4553e2.

The new test convention is now "test/**/test_*.rb" instead of "test/**/*_test.rb". For example, Puma and Minitest are popular repositories using this naming pattern.

https://github.com/seattlerb/minitest really removed the FUD for me when i started learning Ruby and Rails. Its full of metaprogramming and fancy tricks but is also quite small, practical and informal in its style.

e.g. "assert_equal" is really just "expected == actual" at it's core but it uses both both a block param (a kind of closure) for composing a default message and calls "diff" which is a dumb wrapper around the system "diff" utility (horrors!). There is even some evolved nastiness in there for an API change that uses the existing assert/refute logic to raise an informative message. this is handled with a simple if and not some sort of complex hard-to-follow factory pattern or dependency injection misuse.

https://github.com/seattlerb/minitest/blob/master/lib/minite...

Those are just a few examples of what you can do with Minitest! Check out their README on GitHub and keep on exploring.

One of the things I love the most about Ruby is that it tends to coalesce around one or two really popular libraries. Rails is the big one obviously, but over time you see libraries designed for a particular purpose "winning" over other things. This includes things like linting/code analysis (Rubocop), authentication (Devise), testing (RSpec and Minitest) and more. The emphasis is on making something good great rather than making a lot of different good things.

Then try minitest (unit and spec verisons) https://github.com/seattlerb/minitest