Total 53,790 skills, Testing & QA has 1918 skills
Showing 12 of 1918 skills
Use this skill whenever the user wants browser-based end-to-end tests for an Adobe App Builder application. Covers Playwright E2E testing for ExC Shell SPAs, AEM extension UIs, and full-stack flows. Use when the user mentions: "E2E test", "end-to-end test", "Playwright", "browser test", "test my SPA in the browser", "test my AEM extension", "test the full flow", "integration test with UI", "headless browser test", "E2E in CI". This skill is for BROWSER-based testing only. For Jest unit tests of actions or React components, use appbuilder-testing instead.
Zephyr Essential Cloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zephyr Essential Cloud data.
Audits code for test quality and coverage issues — missing tests, test smells, poor test structure, mock abuse, coverage gaps, and fragile test data. Identifies weaknesses in the test suite and generates fix prompts. Trigger phrases: "test quality", "test audit", "test review", "coverage check", "missing tests", "test quality audit".
AI rules for writing tests with Stably Playwright SDK. Use this skill when writing or modifying Playwright tests with Stably AI features. Covers when to use Playwright vs Stably methods, plus minimal patterns for aiAssert, extract, getLocatorsByAI, agent.act, Inbox, and Google auth.
E2E 시나리오 생성, 실행, 자동수정을 통합 처리하는 스킬. "시나리오 만들어줘", "시나리오 실행", "e2e 실행", "E2E 돌려", "시나리오 돌려", "시나리오 변환", "녹화 변환", "e2e 변환", "codegen 변환", "e2e 생성", "시나리오 생성", "시나리오 검증" 키워드로 트리거.
Solidroad platform help — AI-powered QA and training for CX teams. Use when reps ramping too slowly and need AI practice simulations, QA only covers 2% of conversations and you want 100% automated scoring, training and QA are disconnected and insights don't turn into coaching, setting up Solidroad scorecards or custom quality rubrics, connecting Solidroad to Salesforce Service Cloud or Zendesk or Intercom, or evaluating Solidroad vs Observe.AI vs Balto vs Cresta for contact center QA. Do NOT use for general coaching strategy without a specific platform (use /sales-coaching).
Systematically fix all failing tests after business logic changes or refactoring
Browser automation and testing using chrome-devtools MCP server. Use when automating web browsers, taking screenshots, inspecting console logs, monitoring network requests, testing responsive layouts, collecting performance metrics, or debugging web applications. Critical for visual testing workflows and browser-based automation tasks.
Conversational bug discovery → issue draft. Light listening, background exploration, scope assessment. Asks before gh issue create — never auto-files. Use when conducting a QA session, triaging user-reported issues, or filing bugs.
You are **API Tester**, an expert API testing specialist who focuses on comprehensive API validation, performance testing, and quality assurance. You ensure reliable, performant, and secure API int...
Use when adding or updating Go CLI E2E coverage for one `tests/cli_e2e/{domain}` domain of the compiled `lark-cli`, especially when the work requires live `--help` or `schema` exploration, scenario-based `clie2e.RunCmd` workflows, and per-domain `coverage.md` maintenance.
Applitools integration. Manage data, records, and automate workflows. Use when the user wants to interact with Applitools data.