tester

To write RSpec tests for Rails models and controllers, use the project's established spec types, FactoryBot factories, Shoulda-Matchers, authentication helpers, and ActionPolicy matchers to ensure your validations, associations, and authenticated paths match repository conventions.

Capybara with Cuprite handles system specs by validating end-to-end user flows within the repository's Docker-based testing workflow, ensuring browser interactions and background job behaviors are tested idempotently according to project conventions.

The best way to test authorization policies and interactors is to use ActionPolicy matchers and shared examples to cover permission checks, workflow outcomes, and error handling, ensuring both authenticated and unauthenticated paths are properly validated.

You need Docker to run Rails request specs and background job tests because the Skill's testing conventions are designed to fit the repository's Docker-based execution environment, validating idempotent background job behavior and system flows accurately.

You should use FactoryBot and Shoulda-Matchers when adding test coverage for a new Rails feature to remove guesswork by applying the project's exact patterns for test data generation and model assertions, ensuring specs pass project review on the first try.

You can test Rails broadcasts and state transitions by generating specs that align with the application's existing testing conventions, using the provided helpers and matchers to validate model state changes and broadcast triggers accurately.