ruby-testing

RSpec test generation creates unit and Rails-flavored tests using common describe/context/it patterns to cover behavior clearly. You can ask the agent to write these tests for your failing Ruby code to ensure maintainable specs and regression protection.

Diagnosing flaky RSpec test failures involves investigating the failing or flaky tests to propose targeted fixes. This skill guides the investigation of failures, recommends isolation practices, and ensures deterministic setup using time and DB control to resolve flaky behavior.

Yes, this RSpec testing approach works with Ruby 3.2+ projects and supports Factory Bot. It selects appropriate mocking and fixtures for external I/O, applying RSpec conventions to cover scenarios including new test creation and fixing broken specs across your tests.

Fixing broken Rails request specs requires applying explicit stop conditions when test dependencies or testability are unclear. This skill follows explicit guardrails to stop and recommends applying RSpec conventions and appropriate mocking to fix broken specs safely.

You should avoid automated RSpec test generation when test dependencies are missing, requests are ambiguous, or the code is non-testable. The skill uses explicit stop conditions to halt generation when frameworks or dependencies are unclear, preventing unreliable coverage.