SQL and Rust testing guide covering test types, execution, and writing patterns.
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
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add tursodatabase/turso --skill testingCompatible with
Supported agents
Three primary test formats: .sqltest (preferred for SQL compatibility across backends), TCL .test (legacy, being phased out), and Rust integration tests for regression and complex scenarios
Run tests via make test for the full suite, make -C testing/sqltests run-cli for SQL tests, or cargo test for Rust tests
.sqltest format uses simple declarative syntax with @database , test blocks, and expect sections
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontestingExecute the skills CLI command in your project's root directory to begin installation:
epx add tursodatabase/turso --skill testingFetches testing from tursodatabase/turso 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:
.cursor/skills/testing
Restart Cursor to activate testing. Access via /testingin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
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.
testing-strategies
supercent-io/skills-template · Testing · tag: testing
playwright-visual-testing
manutej/luxor-claude-marketplace · Testing · tag: testing
mutation-testing
aj-geddes/useful-ai-prompts · Testing · tag: testing
webapp-testing
composiohq/awesome-claude-skills · Testing · tag: testing
testing-handbook-generator
trailofbits/skills · Testing · tag: testing
playwright-e2e-testing
bobmatnyc/claude-mpm-skills · Testing · tag: testing
testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for testing matched our evaluation — installs cleanly and behaves as described in the markdown.
We added testing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
testing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend testing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend testing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for testing matched our evaluation — installs cleanly and behaves as described in the markdown.
testing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for testing matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 66