Total 54,150 skills, Testing & QA has 1931 skills
Showing 12 of 1931 skills
Write Foundry-based tests and scripts. Trigger phrases - foundry testing, write test, fuzz test, fork test, invariant test, deploy script, gas benchmark, coverage, or when working in tests/ or scripts/ directories.
Validate WCAG 2.1 compliance, screen reader compatibility, and Universal Design for Learning (UDL) principles implementation throughout curriculum materials. Use when checking accessibility, validating UDL, or ensuring compliance. Activates on "accessibility check", "WCAG validation", "UDL review", or "screen reader test".
Guidelines for writing Rust tests.
Senior QA Automation Engineer with 10+ years E2E testing experience. Use when writing end-to-end tests for web apps with Playwright, mobile apps with Detox, testing critical user flows, cross-browser testing, or visual regression testing.
E2E testing for Umbraco backoffice extensions using Playwright and @umbraco/playwright-testhelpers
Run and stabilize iOS tests (XCTest, XCUITest, Swift Testing) on simulators and devices with xcodebuild/simctl: choose destinations, manage simulator state, control flakes (locale/time/network/animations), configure CI, and collect/parse xcresult artifacts.
Automatically discover debugging and profiling skills when working with GDB, LLDB, breakpoints, profiling, stack traces, memory leaks, core dumps, or performance profiling. Activates for debugging development tasks.
Generates end-to-end tests using Playwright with the "given/should" prose format. Use when writing e2e tests for user flows, page interactions, or integration scenarios that exercise the full application stack.
[Testing] ⚡ Run tests locally and analyze the summary report.
Builds end-to-end browser tests for critical user flows using Playwright or Cypress. Includes selector strategies, test data management, page objects, and visual regression testing. Use for "E2E testing", "browser tests", "Playwright", or "Cypress tests".
Browser automation toolkit using Playwright MCP for testing web applications. Use when asked to navigate pages, click elements, fill forms, take screenshots, verify UI components, check console logs, debug frontend issues, or validate responsive design. Supports live browser interaction and accessibility snapshots.
Use when writing, reviewing, or debugging Jest + React Testing Library tests, before writing test code or when tests fail