stimulus_spec 0.7.0 → 0.8.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 31b3ef6e3b0ef09e3f6353d975ee2a65dd7c42dbc4d3be8aa78c7508b88d9ba7
-  data.tar.gz: 5f79191a5baccfabe6a8502fa8708248dc71efe1ba63d87f816a2c882ad5e941
+  metadata.gz: '0912c1fbe8ee121aa811782e445be9524634567f4b19b59e8921c8c8fd196f39'
+  data.tar.gz: c4b7149d6711bcfbda89a04d2b7095fd7996dfa8ff4adb95d034b15885ea1c9e
 SHA512:
-  metadata.gz: 6b789aa21b411f503223b5c6116507f48168cfd675ea198c4c3a8cf68490754ebcaf0bcdea718c4cf492400cf3df6eba5d0079c41b2e2ce48020165b6b4bb348
-  data.tar.gz: 97623a443042991da1c942449406f0e92c0b8918d8a9bdbd8b001962c0c238db103d0d2cc9d27a3aff05bd75256d65b593686876fd731f883f8a5c0547af9d0d
+  metadata.gz: 0d84919b59c7d2c1bfafde03194f9db337e4cb78fb25f9f65746fa6cf35b839ca495ffa7a57fe577c0c5e93be98c1993f7fe4d572013cc6f988a02b41b70830e
+  data.tar.gz: 7d284dc0aba931a47d44b13e5a563372957b1ef063db08284e1fad073247f482b915d694efb561e78670840af09edc02860971b00d3194ed7675348e087ba7a8

data/CHANGELOG.md

@@ -7,6 +7,21 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.8.1] - 2026-06-30
+
+### Fixed
+
+- Guard matcher requires and `RSpec.configure` behind `defined?(RSpec::Core)` so the gem is safe to auto-require in non-test contexts (e.g. asset precompilation). Previously, a partial load of `rspec-expectations` or `rspec-mocks` could define the `RSpec` constant without `RSpec::Core`, causing a `NoMethodError` when `RSpec.configure` was called. Nokogiri is now also only required when RSpec::Core is present.
+
+## [0.8.0] - 2026-06-23
+
+### Added
+
+- `bin/benchmark` script for measuring matcher overhead
+- Version spec enforcing semver format on `StimulusSpec::VERSION`
+- `docs/migration_guide.md` for migrating from turbo_rspec's Stimulus matchers
+- Guiding principles section in README
+
 ## [0.7.0] - 2026-06-23
 
 ### Added
@@ -61,7 +76,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `have_stimulus_action(descriptor)` matcher — full descriptor (`~=`) and shorthand without event (`*=`)
 - `have_stimulus_target(controller, target)` matcher — asserts `[data-{controller}-target~="target"]`
 
-[Unreleased]: https://github.com/eclectic-coding/stimulus_spec/compare/v0.7.0...HEAD
+[Unreleased]: https://github.com/eclectic-coding/stimulus_spec/compare/v0.8.1...HEAD
+[0.8.1]: https://github.com/eclectic-coding/stimulus_spec/releases/tag/v0.8.1
+[0.8.0]: https://github.com/eclectic-coding/stimulus_spec/releases/tag/v0.8.0
 [0.7.0]: https://github.com/eclectic-coding/stimulus_spec/releases/tag/v0.7.0
 [0.6.0]: https://github.com/eclectic-coding/stimulus_spec/releases/tag/v0.6.0
 [0.5.0]: https://github.com/eclectic-coding/stimulus_spec/releases/tag/v0.5.0

data/ROADMAP.md

@@ -1,8 +1,3 @@
 # stimulus_spec Roadmap
 
-## 1.0.0 — Stable API
-
-- API freeze — public method signatures are part of the semver contract
-- `bin/benchmark` — matcher overhead measurement
-- Version spec (semver format enforced)
-- `docs/migration_guide.md` — migrating from turbo_rspec's Stimulus matchers to stimulus_spec
+All planned milestones through 0.8.0 have been completed. Gathering user feedback before a 1.0.0 release.

data/docs/migration_guide.md

@@ -0,0 +1,84 @@
+# Migrating from turbo_rspec to stimulus_spec
+
+[turbo_rspec](https://github.com/eclectic-coding/turbo_rspec) includes basic Stimulus matchers: `have_stimulus_controller`, `have_stimulus_action`, and `have_stimulus_target`. **stimulus_spec** provides the same three matchers plus `have_stimulus_value`, `have_stimulus_class`, `have_stimulus_outlet`, multi-controller assertions, and scoped matching.
+
+Both gems can coexist — they use separate namespaces (`TurboRspec::Matchers` vs `StimulusSpec::Matchers`) and won't conflict. You can migrate incrementally.
+
+## Step 1: Add stimulus_spec
+
+```ruby
+# Gemfile
+group :test do
+  gem "stimulus_spec"
+end
+```
+
+```bash
+bundle install
+```
+
+With `stimulus-rails` in your bundle, `stimulus_spec` auto-includes its matchers into request, controller, system, and feature specs. No configuration needed.
+
+## Step 2: Verify existing tests pass
+
+Your existing turbo_rspec Stimulus matchers (`TurboRspec::Matchers`) will continue to work alongside `StimulusSpec::Matchers`. Run your test suite to confirm nothing breaks:
+
+```bash
+bundle exec rspec
+```
+
+## Step 3: Switch namespaces (optional)
+
+If you manually include turbo_rspec's Stimulus matchers, update to the stimulus_spec equivalents:
+
+```ruby
+# Before
+config.include TurboRspec::Matchers, type: :request
+
+# After
+config.include StimulusSpec::Matchers, type: :request
+config.include StimulusSpec::Capybara::Matchers, type: :system
+```
+
+If you rely on auto-include (the default for both gems), this step is unnecessary — both sets of matchers are already available.
+
+## Step 4: Use new matchers
+
+With stimulus_spec installed, you now have access to matchers that turbo_rspec doesn't provide:
+
+```ruby
+# Value assertions
+expect(response).to have_stimulus_value("search", "url", "/results")
+
+# CSS class assertions
+expect(response).to have_stimulus_class("search", "loading", "opacity-50")
+
+# Outlet assertions
+expect(response).to have_stimulus_outlet("search", "results", "#results-list")
+
+# Multi-controller on a single element
+expect(response).to have_stimulus_controller("hello", "clipboard")
+
+# Scoped matching
+expect(response).to have_stimulus_controller("search").within(".search-form")
+```
+
+## Matcher comparison
+
+| Matcher | turbo_rspec | stimulus_spec |
+|---|---|---|
+| `have_stimulus_controller` | Single name | Single or multiple names |
+| `have_stimulus_action` | Full or shorthand | Full or shorthand |
+| `have_stimulus_target` | Controller + target | Controller + target |
+| `have_stimulus_value` | — | Existence or equality |
+| `have_stimulus_class` | — | Existence or equality |
+| `have_stimulus_outlet` | — | Existence or selector |
+| `.within(selector)` | — | All matchers |
+| Capybara variants | Controller, action, target | All six matchers |
+| Failure messages | Basic | Shows found values and HTML context |
+
+## Step 5: Remove turbo_rspec Stimulus matchers (optional)
+
+If you want to fully consolidate, you can stop including turbo_rspec's Stimulus matchers. turbo_rspec's Turbo-specific matchers (`have_turbo_frame`, `have_turbo_stream`, etc.) are unaffected — only the Stimulus matchers overlap.
+
+If you use turbo_rspec solely for Turbo matchers, no changes are needed. Both gems coexist cleanly.

data/lib/stimulus_spec/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module StimulusSpec
-  VERSION = "0.7.0"
+  VERSION = "0.8.1"
 end

data/lib/stimulus_spec.rb

@@ -2,8 +2,6 @@
 
 require_relative "stimulus_spec/version"
 require_relative "stimulus_spec/configuration"
-require_relative "stimulus_spec/matchers"
-require_relative "stimulus_spec/capybara/matchers"
 
 # RSpec matchers for testing Stimulus controller wiring in Rails applications.
 #
@@ -62,7 +60,10 @@ module StimulusSpec
 end
 
 # :nocov:
-if defined?(RSpec)
+if defined?(RSpec::Core)
+  require_relative "stimulus_spec/matchers"
+  require_relative "stimulus_spec/capybara/matchers"
+
   RSpec.configure do |config|
     StimulusSpec.install_rspec_integration(config)
   end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: stimulus_spec
 version: !ruby/object:Gem::Version
-  version: 0.7.0
+  version: 0.8.1
 platform: ruby
 authors:
 - Chuck Smith
@@ -45,6 +45,7 @@ files:
 - Rakefile
 - codecov.yml
 - docs/cookbook.md
+- docs/migration_guide.md
 - lib/stimulus_spec.rb
 - lib/stimulus_spec/capybara/matchers.rb
 - lib/stimulus_spec/capybara/matchers/have_stimulus_action.rb