Apply Rails testing standards with Minitest, fixtures, and pragmatic coverage boundaries. Use when creating tests, reviewing test quality, or improving flaky and slow Rails test suites.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrails-testingExecute the skills CLI command in your project's root directory to begin installation:
Fetches rails-testing from marckohlbrugge/37signals-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate rails-testing. Access via /rails-testing in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
612
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
612
stars
| name | rails-testing |
| description | Apply Rails testing standards with Minitest, fixtures, and pragmatic coverage boundaries. Use when creating tests, reviewing test quality, or improving flaky and slow Rails test suites. |
| disable-model-invocation | true |
Use for test-writing and test-review tasks. Patterns from Campfire and Fizzy test suites.
parallelize(workers: :number_of_processors).created_at: <%= 1.hour.ago %>) and shared computed values (one bcrypt digest reused).app/models structure in test/models: app/models/card/closeable.rb ↔ test/models/card/closeable_test.rb; shared concerns under test/models/concerns/..first/.last are stable and runtime records are always newer.ActionText::Attachment.from_attachable(user).to_html), not hand-written markup.travel_to for time-based logic.SecureRandom); use VCR for external HTTP — auto-name cassettes from class+test name, normalize timestamps in matching.perform_enqueued_jobs(only: SpecificJob) and assert_enqueued_with — not by unit-testing trivial job classes.assert_difference({ -> { card.assignees.count } => -1, -> { Event.count } => +1 }).as: :turbo_stream (assert stream targets) and as: :json (status, Location header, body).assert_turbo_stream_broadcasts in model tests, assert_turbo_stream action:, target: in controller tests, assert_no_turbo_stream_broadcasts for negatives.Current.account (and Current.session when behavior depends on the actor) in setup; integration/system tests set default_url_options[:script_name]; provide an untenanted { } helper for auth routes. Clear Current in teardown.Rack::MockRequest.using_session("Kevin") for multi-user scenarios; wait for cable connection before asserting realtime; auth via a fast session-transfer helper, keeping the full login flow to one smoke test.self.use_transactional_tests = false + explicit cleanup.ActionCable.server.pubsub, Current).travel_to.Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
marckohlbrugge/37signals-skills
marckohlbrugge/37signals-skills
marckohlbrugge/37signals-skills
marckohlbrugge/37signals-skills
marckohlbrugge/37signals-skills
marckohlbrugge/37signals-skills
Useful defaults in rails-testing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in rails-testing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added rails-testing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: rails-testing is the kind of skill you can hand to a new teammate without a long onboarding doc.
rails-testing has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend rails-testing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: rails-testing is focused, and the summary matches what you get after install.
Keeps context tight: rails-testing is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added rails-testing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in rails-testing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 52