Loading...
Loading...
Found 19 Skills
Write usability test scenarios with tasks, success criteria, and observation guides.
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
Apifox Test Scenario Modeling: Query, create, update, delete and run test-scenario; Import endpoints, single-interface test cases or other scenario steps; Add scenario reference steps; Best practices for complex step orchestration, connection of steps such as interface steps/conditions/loops/waiting/scripts/databases, pre/post operations, variable references, assertions, extractors and scenario debugging. Used when users need to create or maintain complex automated testing workflows.
Creates comprehensive load test plans with realistic scenarios, traffic models, k6 scripts, and success criteria. Use for "load testing", "performance testing", "capacity validation", or "stress testing".
End-to-end testing scenarios for Supabase - complete workflow tests from project creation to AI features, validation scripts, and comprehensive test suites. Use when testing Supabase integrations, validating AI workflows, running E2E tests, verifying production readiness, or when user mentions Supabase testing, E2E tests, integration testing, pgvector testing, auth testing, or test automation.
Apifox Automated Test Execution, Suites & CI: test-suite, scheduled-task, runner, apifox run, execution parameters, iteration data, report upload and CI regression. For complex test-scenario step modeling, please use apifox-test-scenario.
Run and test HTTP requests with Hurl. Use when working with HTTP APIs, testing web services, or creating HTTP-based test scenarios. Hurl allows you to define HTTP requests in plain text files and validate responses with asserts and captures.
Write BDD test scenarios in Gherkin for a feature
Layer 4 artifact for Behavior-Driven Development test scenarios using Gherkin Given-When-Then format
Use when the user asks to "create an evaluator", "create evals", "create a scenario", "write a test scenario", "design a test case", "test my agent", "build eval coverage", "plan a test suite", "create red team tests", "set up test profiles", "configure conditional actions", "write a conditional action evaluator", "build a deterministic test", "design an IVR test", "IVR navigation test", "write a unit test for a voice agent", "build a regression test", "scripted scenario", "scripted voice test", "structured evaluator", "exact flow test", "sequential conditions", "fixed sequence test", or "run evals". Covers individual evaluator design, suite coverage strategy, test profiles, mock-tool data design, conditional actions (deterministic / unit test / regression / IVR navigation flows), and best practices for workflow / red-team / edge-case / deterministic test types.
Cucumber best practices, patterns, and anti-patterns
Use this skill when you need to create high-quality test cases with normal, exception, and boundary scenarios; triggers include test case writing and test design.