cursorrules
457Cursor rule Cursor
When the user asks about mock server, use mock-server-ai-mcp tools: createendpoint, listendpoints, generatemockdata, validateschema.
1,973 tagged Testing, measured the same way as everything else here.
Browse within: ai-coding 154cursor-ai 145cursor-ide 117code-quality 1091c-enterprise 78cursorrules 78hacktoberfest 67hacktoberfest2022 64yaxunit 64cursor-rules 62loggy-core 46loggy-terminal 46awesome-list 33model-context-protocol 33
Cursor rule Cursor
When the user asks about mock server, use mock-server-ai-mcp tools: createendpoint, listendpoints, generatemockdata, validateschema.
Cursor rule Cursor
Make sure to re-run tests whenever you make a change to the the source code and also ensure that the test cases are up to date.
Cursor rule Cursor
use vitest as test framework.
Cursor rule Cursor
The MCP project uses pytest for testing with specific patterns for test organization and implementation, along with static type checking using mypy.
jairosoft-com/mcp-server-template-python
Cursor rule Cursor
Your Role and Mission: You are an expert TDD Software Developer AI specializing in Python. Your primary function is to write Python code by strictly adhering to the Test-Driven Development (TDD) methodology using the pytest framework. Your goal is to produce high-quality, robust, maintainable, and well-documented…
Cursor rule Cursor
Cursor rule "cursorrules" from bkotos/todoist-mcp, covering todoist mcp server - development standards, tdd approach, architecture, code style and testing.
Cursor rule Cursor
A set of testing rules for projects using Vitest, a JavaScript and TypeScript test framework. It specifies Vitest, Node.js, fetch setup, string comparisons, and isolated test stubs.
Cursor rule Cursor
Use this rule when asked to test changes and functionality of the product.
Cursor rule Cursor
Never use synthetic, mock, or dummy data; use hypothesis + experiment + evidence instead; always include a review-changes step that peer-reviews and reproduces results and accepts or rejects premises.
Cursor rule Cursor
USE ALWAYS when writing new features, fixing bugs, or refactoring to ensure changes are verified and regressions are prevented.
Cursor rule Cursor
When I am not just asking a question, but we're building a new feature, then I would like you to always use TDD.
Cursor rule
VisualQ QA agent — org MCP key workflows (VRT, FRT, onboarding).
Cursor rule Cursor
Never try to run a test-script from commandline using node -e. This will always fail, you'll need to write a typescript test file, build that and execute that.
Cursor rule Cursor
Run code you wrote before claiming it works.
Cursor rule Cursor
Zama fhEVM testing rules — applies to test files. Covers Hardhat mock mode, encrypted input, decryption APIs, and common test patterns.
Cursor rule
Playwright MCP — trigger and closed-loop workflow for automated test repair.
Cursor rule
Playwright test standards — locator rules, DSL conventions, tag format.
Cursor rule Cursor
Remote-ready MCP server for Hevy workout data — full API coverage via chrisdoc/hevy-mcp, with Streamable HTTP transport and OAuth for use in claude.ai (web, mobile, Desktop). Deploys to Railway.
Cursor rule Cursor
Make sure to re-run tests whenever you make a change to the the source code and also ensure that the test cases are up to date.
Cursor rule Cursor
Use UPilot MCP for Unity Editor automation.
Cursor rule
Same shape as the reference spec, but asserts one rule id with no mechanized Validator behind it yet — must be flagged for mechanization, never silently accepted as enforced.
Cursor rule
Neutral fixture form of the ingested reference spec (docs/plans/enforcer-selfhost-plan/refs/security-testing-source.md) §2.3 invariants and §3.1-3.20 required test categories, plus a representative set of backed Track H rule assertions. No product/company/game branding.
Cursor rule Cursor
Quality harness for MCP NetSuite practice — layers, RBAC, secrets, tests.
Cursor rule Cursor
QA workflow for reviewing stories, designing tests, and reporting verified defects.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: