Loading...
Loading...
Found 29 Skills
This skill should be used when the user asks to "write tests", "add tests", "test coverage", "run tests", "debug failing tests", "mock functions", or mentions Vitest, unit tests, component tests, test-driven development, or testing utilities. Provides comprehensive Vitest v4 guidance for TypeScript React/Next.js projects.
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
Write a playwright test, make sure it runs, and is not flaky.
Skill for Playwright-driven web UI testing, exploration, test generation, execution, and debugging (TypeScript or Python). Triggers for tasks involving application testing, validation, test generation, or UI automation in web applications.
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.
Run e2e tests in the Studio app. Use when asked to run e2e tests, run studio tests, playwright tests, or test the feature.
Helps debug test failures and view logs in the SnapLogic Robot Framework project. Use when the user wants to view test results, check container logs, debug specific test failures, or run environment diagnostics.
Systematically trace bugs backward through call stack to find original trigger. Use when errors occur deep in execution and you need to trace back to find the original trigger.
Use when writing, reviewing, or debugging Jest + React Testing Library tests, before writing test code or when tests fail
Testing guide using Vitest. Use when writing tests (.test.ts, .test.tsx), fixing failing tests, improving test coverage, or debugging test issues. Triggers on test creation, test debugging, mock setup, or test-related questions.
Evidence-based test debugging enforcing systematic root cause analysis. Use when tests are failing, pytest errors occur, test suite not passing, debugging test failures, or fixing broken tests. Prevents assumption-based fixes by enforcing proper diagnostic sequence. Works with Python (.py), JavaScript/TypeScript (.js/.ts), Go, Rust test files. Supports pytest, jest, vitest, mocha, go test, cargo test, and other frameworks.
Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".