Vanilla Rails Testing FAQs

Question 1

How does it handle controller testing?

Accepted Answer

It enforces the use of ActionDispatch::IntegrationTest, which tests the full request cycle including routing and middleware, rather than the more isolated and now-discouraged ActionController::TestCase.

Question 2

Does this skill support RSpec or FactoryBot?

Accepted Answer

No. This skill specifically enforces the 'Vanilla Rails' philosophy, which explicitly rejects RSpec and FactoryBot in favor of Minitest and native Rails fixtures.

Question 3

Why does the skill require Current.session in model tests?

Accepted Answer

Many Rails models rely on CurrentAttributes for auditing, authorization, and event tracking. Setting Current.session in the setup ensures the model has the necessary context to function as it would in a real request.

Question 4

What is the primary benefit of using fixtures over factories?

Accepted Answer

Fixtures are faster because they are loaded once into the database and they force developers to think about realistic, persistent data scenarios rather than ephemeral test-only objects.

Question 5

What happens if I try to use 'describe' or 'it' blocks?

Accepted Answer

Claude will identify these as RSpec patterns and automatically rewrite them into Minitest 'test' blocks and 'setup' methods to comply with the Vanilla Rails standard.

Vanilla Rails Testing

Key Features

Use Cases

Vanilla Rails Testing

Key Features

Use Cases