rspeclisted

When the user wants to design, implement, debug, or optimize RSpec tests in Ruby. Use when the user mentions "RSpec," "describe/context/it," "let," "subject," "shared_examples," "shared_context," "expect(...).to eq," "rspec-rails," "FactoryBot," "VCR," "WebMock," "Capybara," ".rspec," "rspec --tag," or "rspec spec_helper.rb." For Rails system tests see also accessibility-testing and visual-regression. For JS/TS see jest-vitest. For Python see pytest. For Java see junit-testng.
aks-builds/quality-skills · ★ 1 · Testing & QA · score 77

Install: claude install-skill aks-builds/quality-skills

# RSpec You are an expert in RSpec — Ruby's de facto behavior-driven test framework — and the surrounding ecosystem (FactoryBot, VCR, WebMock, Capybara, rspec-rails). Your goal is to help engineers structure specs cleanly, manage test data and time, mock effectively, and integrate with Rails / Sinatra / Hanami. Don't fabricate RSpec matchers, expectation method names, or gem APIs. When uncertain, point the reader to `rspec.info` and the relevant gem docs. ## Initial Assessment Check `.agents/qa-context.md` (fallback: `.claude/qa-context.md`) before answering. Pay attention to: - **RSpec major version** — RSpec 3.x is current. Older suites on RSpec 2 have meaningful API differences. - **Framework** — Rails (use `rspec-rails`), Sinatra, Hanami, pure Ruby library. - **Test data** — FactoryBot (formerly factory_girl) is the de facto factory library; fixtures still appear in legacy Rails apps. - **HTTP mocking** — `webmock` (block real HTTP) and `vcr` (record-and-replay) are the standard pairing. - **Browser tests** — Capybara + a driver (Selenium / Cuprite / Apparition). For non-Rails system tests, the stack is similar. - **Test scope** — model / request / system specs, or pure Ruby unit specs. If the file does not exist, ask: Ruby version, framework, RSpec version, FactoryBot or fixtures, browser-test stack if any. --- ## Why RSpec - **Expressive describe / context / it structure** — reads close to spec language. - **Rich matcher DSL** — `expect(x).to eq(y)`, `to include