minitest-strict 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ab7f3cff1adfd1e6a69afec2832299ca911bf2732cb3c205c9c116edfaf094eb
-  data.tar.gz: 8f45b484e5c08cd7c25498c028ff3f00540ef5b494561adbe964917fb2ebff87
+  metadata.gz: 90ddd99c8cc1dc80b143781ccc85afc25955ffa31a208f4830662eeda3651675
+  data.tar.gz: 58edeab6ae51aff0ea36561977e014080eaf571155289286eb1748d59b5b4a9c
 SHA512:
-  metadata.gz: 2e7508a3ff72d562ca069ea2fa8a5b9330ff6066121beb8f4162849673cac097dbb2cceba10b8a03884a90285f11924846763bd834c1b56029bf87240e76544e
-  data.tar.gz: bef6939ad19d6ecfea699367bbfd51f69e9a0fee664927f14ff254d0efe349e0403443c5c34804d290810fbe7974c687007958e547ae646c40bb590c038fa8bd
+  metadata.gz: 324e9e939b2d0d8d10d74b8717c72d8f9b9bed618444b38fea9f11bf124bceedd19e9c7b462e030d51a26e36261d31ccf576ea261bd8cd97c23fd68412db2c68
+  data.tar.gz: 901e6a061d0e4fca71352243896314df7268930f93bf95f5ea0e37dd71ea8c62cacb0cdbd19b66d865a67fb7b841be5071d341bf43f4c0fc33b902711f9a6cdb

data/CHANGELOG.md

@@ -5,6 +5,16 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.0.1] - 2026-07-26
+
+### Fixed
+
+- `refute_match` no longer always fails on Minitest 6, which reimplemented it
+  via `refute_operator`. Since `=~` returns `nil` or an `Integer` — never
+  `false` — the strict `refute_operator` rejected every non-match.
+  minitest-strict now defines `refute_match` directly, restoring the standard
+  Minitest 5 behavior. ([#1](https://github.com/sferik/minitest-strict/issues/1))
+
 ## [1.0.0] - 2026-02-26
 
 ### Added

data/README.md

@@ -117,6 +117,13 @@ refute_predicate 0, :nonzero?       # fail — returns nil, not false
 
 ### `assert_operator` / `refute_operator`
 
+> [!WARNING]
+> Operators like `=~` return non-boolean values (`nil` or an `Integer`), so
+> they will always fail with minitest-strict's `assert_operator` and
+> `refute_operator`. Assert on the actual return value instead: use
+> `assert_match` / `refute_match`, or `assert_equal 2, x =~ y` to pin the
+> match position, or `assert_nil x =~ y` for a non-match.
+
 Requires operators to return exactly `true` or `false`.
 
 ```ruby
@@ -131,6 +138,27 @@ obj.define_singleton_method(:<=>) { |_| 1 }
 assert_operator obj, :<=>, 2       # fail — returns 1, not true
 ```
 
+### `refute_match`
+
+> [!NOTE]
+> This one is redefined for compatibility, not strictness. Minitest 6
+> implements `refute_match` via `refute_operator`, but `=~` returns `nil` or
+> an `Integer` — never `false` — so the strict `refute_operator` would reject
+> every non-match. minitest-strict defines `refute_match` directly, preserving
+> the standard behavior on both Minitest 5 and 6.
+
+```ruby
+refute_match(/nope/, "hello world")   # pass
+refute_match(/hello/, "hello world")  # fail
+```
+
+> [!WARNING]
+> Rails aliases `assert_no_match` to `refute_match` when
+> `ActiveSupport::TestCase` loads, and `alias` copies the method body at that
+> moment. On Minitest 6, require `minitest/strict` **before**
+> `rails/test_help` so `assert_no_match` picks up the fixed implementation —
+> or use `refute_match` directly.
+
 ### `assert_nil` / `refute_nil`
 
 > [!NOTE]

data/lib/minitest/strict/version.rb

@@ -3,6 +3,6 @@ module Minitest # :nodoc:
   # Version information for minitest-strict.
   module Strict
     # Current version of minitest-strict.
-    VERSION = "1.0.0".freeze
+    VERSION = "1.0.1".freeze
   end
 end

data/lib/minitest/strict.rb

@@ -120,6 +120,21 @@ module Minitest
       assert_equal false, o1.__send__(op, o2), msg
     end
 
+    ##
+    # Fails if +matcher+ matches +obj+. Redefined because Minitest 6
+    # implements this via refute_operator, but <tt>=~</tt> returns nil
+    # or an Integer -- never +false+ -- so the strict refute_operator
+    # above would fail even when +matcher+ does not match. There is no
+    # boolean contract to enforce here, so this restores the standard
+    # Minitest 5 behavior.
+
+    def refute_match matcher, obj, msg = nil
+      assert_respond_to matcher, :=~
+      msg = message(msg) { "Expected #{mu_pp matcher} to not match #{mu_pp obj}" }
+      matcher = Regexp.new Regexp.escape matcher if matcher.is_a?(String)
+      refute matcher =~ obj, msg
+    end
+
     ##
     # Fails unless +obj+ is nil. Uses +equal?+ for identity check.
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: minitest-strict
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Erik Berlin
@@ -42,7 +42,7 @@ files:
 - README.md
 - lib/minitest/strict.rb
 - lib/minitest/strict/version.rb
-homepage: https://github.com/sferik/minitest-strict
+homepage: https://sferik.github.io/minitest-strict
 licenses:
 - MIT
 metadata:
@@ -65,7 +65,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.6
+rubygems_version: 4.0.17
 specification_version: 4
 summary: Strict assertions for Minitest
 test_files: []