exploratory-test

Solid

Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Deeper than /smoke-test. Use when the user asks to "exploratory test", "test thoroughly", "test all scenarios", "deep test", "test edge cases", "test everything", "break it", or "find bugs by testing".

Testing & QA 312 stars 24 forks Updated today MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
83
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Exploratory Test Execute multi-level exploratory testing that goes beyond smoke testing to actively find bugs through escalating test scenarios. ## Step 1: Load or Create Test Plan Check if `.turbo/test-plan.md` exists. - **If it exists** — read the test plan and continue to Step 2. If the user specifies a narrower scope, filter the plan to relevant scenarios rather than executing all of them. - **If it does not exist** — run the `/create-test-plan` skill first, then continue. ## Step 2: Determine Testing Approach Use the approach specified in the test plan. If the plan does not specify one, determine it using the same logic as `/create-test-plan` Step 3. ## Step 3: Execute Tests by Level Work through each level sequentially. Complete all tests in a level before moving to the next. ### Execution Loop (Per Test) 1. Set up the preconditions described in the test scenario 2. Perform the exact steps 3. Capture the result (screenshot, output, or state observation) 4. Compare against the expected outcome 5. Record **PASS** or **FAIL** with details ### Level Progression 1. **Level 1: Basic Functionality** — If any Level 1 test fails, report early and use `AskUserQuestion` to ask whether to continue. Basic failures may indicate the feature is too broken for deeper testing. 2. **Level 2: Complex Operations** — Execute all tests regardless of individual failures. 3. **Level 3: Adversarial Testing** — Execute all tests. Failures here are expected and valuable. 4. **Level 4...

Details

Author
tobihagemann
Repository
tobihagemann/turbo
Created
2 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Solid

comprehensive-test

Execute comprehensive, multi-level testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Deeper than /smoke-test. Use when the user asks to "test thoroughly", "comprehensive test", "test all scenarios", "deep test", "test edge cases", "test everything", "break it", or "find bugs by testing".

312 Updated today
tobihagemann
Testing & QA Solid

create-test-plan

Analyze what changed and generate a structured test plan at .turbo/test-plan.md covering four escalating levels: basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Use when the user asks to "create a test plan", "plan tests", "what should I test", "generate test scenarios", "test plan for this PR", or "what are the test cases".

312 Updated today
tobihagemann
Testing & QA Solid

smoke-test

Launch the app and hands-on verify that it works by interacting with it. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does it actually work". Not for unit/integration tests.

312 Updated today
tobihagemann
Testing & QA Listed

test-pilot-loop

Test-pilot any running app through computer use. Trigger when a build completes, user says "test pilot this", "test my app", "quick flight", "run a flight check", or "check the UX". Tests with three knowledge tiers (knows nothing, has manual, has PRD) and reports UX findings with a Tier Gap Ratio.

0 Updated today
prasunicecold140
Testing & QA Listed

qa-testing

Run QA testing on a page, feature, or full site at one of three depth tiers (smoke, standard, full). Use this skill whenever the user asks to test a page, audit a site, check for bugs, verify a deploy, run a QA sweep, or review accessibility, performance, or SEO basics. Triggers on test, QA, audit, verify, check, is it working, does it look right, broken, 404, image not loading, post-deploy check, regression test. Also triggers proactively after any significant code change or new page launch where verification matters.

2 Updated yesterday
rampstackco