vanilla-rails-testing

Included with Lifetime

$97 forever

Use when writing Rails tests - enforces fixtures-only, integration-style controller tests, Current.session setup, simple naming, and Minitest syntax (NO FactoryBot, NO RSpec)

Writing & Docs

What this skill does


# Vanilla Rails Testing

**NO FACTORYBOT. NO RSPEC. NO DATA CREATION IN TESTS.**

## Banned → Required

| Never use | Use instead |
|-----------|-------------|
| `create(:model)`, `build(:model)`, FactoryBot | Fixtures: `cards(:logo)` |
| `let`, `describe`, `it`, `context`, `subject` | `test "name"`, `setup do` |
| `expect(...).to`, `.should` | `assert`, `assert_equal`, `assert_not` |
| `refute` | `assert_not` |
| `ActionController::TestCase` | `ActionDispatch::IntegrationTest` |
| `before_each` | `setup do` |
| RSpec mocks (`allow`, `expect`) | Mocha (`.stubs`) |

If any banned pattern appears, delete it and rewrite.

## Fixtures Only

```ruby
test "close card" do
  cards(:logo).close
  assert cards(:logo).closed?
end
```

Fixture missing? Add it to the fixtures file. Never create data in tests.

## Controller Tests = Integration Tests

```ruby
class Cards::ClosuresControllerTest < ActionDispatch::IntegrationTest
  setup do
    sign_in_as :kevin
  end

  test "create" do
    post card_closure_path(cards(:logo)), as: :turbo_stream
    assert_response :success
  end
end
```

## Model Tests Require Current.session

Always set `Current.session` in setup, even if you think it's not needed:

```ruby
class Card::CloseableTest < ActiveSupport::TestCase
  setup do
    Current.session = sessions(:david)
  end

  test "close records user" do
    cards(:logo).close(user: users(:kevin))
    assert_equal users(:kevin), cards(:logo).closed_by
  end
end
```

## Assertion Patterns

**State changes:** `assert_difference` with lambda syntax:

```ruby
assert_difference -> { Card.count }, +1 do
  post board_cards_path(boards(:writebook))
end

assert_difference({
  -> { cards(:logo).events.count } => +1,
  -> { Event.count } => +1
}) do
  cards(:logo).close(user: users(:kevin))
end
```

**Boolean toggles:** `assert_changes`:

```ruby
assert_changes -> { cards(:logo).reload.closed? }, from: false, to: true do
  post card_closure_path(cards(:logo)), as: :turbo_stream
end
```

**Exceptions:** `assert_raises`:

```ruby
assert_raises ActiveRecord::RecordNotFound do
  Card.find("nonexistent")
end
```

## Test Names

Concise. File + method name provide context.

```ruby
# Good
test "create"
test "close records user"

# Bad
test "should create a new card when given valid parameters"
```

## System Tests

Same rules — fixtures, no data creation:

```ruby
class SmokeTest < ApplicationSystemTestCase
  test "create a card" do
    sign_in_as(users(:david))
    visit board_url(boards(:writebook))
    click_on "Add a card"
  end
end
```

## Stubbing

Use mocha for stubs, webmock for HTTP:

```ruby
TestMailer.stubs(:goes_boom).raises(Net::SMTPSyntaxError)
stub_request(:post, webhook.url).to_return(status: 200)
```

## Red Flags

| Red flag | Action |
|----------|--------|
| `create(:model)` or `FactoryBot` | Delete. Use fixtures. |
| `describe`, `it`, `context` | Delete. Use `test`. |
| `expect(...).to` | Delete. Use `assert`. |
| Model test without `Current.session` | Add `Current.session = sessions(:fixture)` |
| Test names starting with "should" | Shorten. |
| Data creation in tests | Add fixture instead. |

Files: 1

Size: 3.3 KB

Complexity: 7/100

Category: Writing & Docs

Source: https://github.com/zemptime/zemptime-marketplace/tree/main/vanilla-rails/skills/testing

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts