spree-testing

Spree Testing

Layer	Tooling
Rails app (server/)	RSpec + Factory Bot + spree_dev_tools — not Minitest, not fixtures
Dashboard (apps/dashboard)	Vitest (unit) + Playwright (e2e), preconfigured
Storefront (apps/storefront)	whatever the Next.js app ships with

Spree has no server-rendered admin or storefront, so there are no Capybara feature specs to write for Spree screens. Browser coverage belongs to Playwright against the dashboard/storefront.

Setup

Projects from create-spree-app arrive with RSpec configured. For a classic app:

# Gemfile
group :development, :test do
  gem 'spree_dev_tools'
end

bin/rails g spree_dev_tools:install

The generator runs rspec:install if needed and writes spec/support/{spree,factory_bot,database_cleaner,active_job}.rb. spec/support/spree.rb loads:

• Spree's factories (spree/testing_support/factories) + FactoryBot syntax
• spree/testing_support/store — a default USD store (@default_store) created before each group and cleaned after each example
• Spree::TestingSupport::Preferences (reset_spree_preferences before each example)
• spree/api/testing_support/v3/base — the API v3 shared contexts and JWT helper
• json_response for type: :request and type: :controller
• ActiveJob::TestHelper, DatabaseCleaner (transaction strategy)

Factory decorators in spec/factories/spree/**/*_decorator.rb are loaded automatically.

Running

spree rspec                                       # whole suite, in the web container, RAILS_ENV=test
spree rspec spec/models/spree/brand_spec.rb:15    # file / line; any rspec flags pass through
bundle exec rspec …                               # classic app, from the app root

spree rspec works from a cold stack (it falls back to a one-off container). After adding migrations in a classic app: bin/rails db:test:prepare.

Factories you'll use

Read the source when in doubt: $(bundle show spree_core)/lib/spree/testing_support/factories/.