Total 30,439 skills, Testing & QA has 1234 skills
Showing 12 of 1234 skills
Add Playwright QA tests to a game — visual regression, gameplay verification, performance, and accessibility
Smoke test for alicloud-media-vod. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-compute-fc-agentrun. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-ai-cloud-call-center. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-ai-contactcenter-ai. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-observability-pts. Validate script compilation and one bounded read-only PTS metadata query path.
Cross-browser, cross-platform, and cross-device compatibility testing ensuring consistent experience across environments. Use when validating browser support, testing responsive design, or ensuring platform compatibility.
Comprehensive Salesforce testing skill with test execution, code coverage analysis, and agentic test-fix loops. Run Apex tests, analyze coverage, generate test patterns, and automatically fix failing tests with 120-point scoring.
Playwright browser automation API, web scraping, and tooling. Covers locator strategies, assertions, API testing, stealth mode, anti-bot bypass, authenticated sessions, screenshots/PDFs, Docker deployment, configuration, debugging, and MCP integration with AI agents. Prevents documented errors including CI timeout hangs, extension testing failures, and navigation issues. Use when automating browsers, scraping protected sites, bypassing bot detection, generating screenshots/PDFs, configuring Playwright Test, troubleshooting Playwright errors, or learning Playwright API patterns. For E2E test architecture, Page Object Models, CI sharding strategies, or test organization patterns, use the e2e-testing skill instead.
Quality Assurance & Advanced Testing
Configure specific Sentry features beyond basic SDK setup. Use when asked to monitor AI/LLM calls, set up OpenTelemetry pipelines, or create alerts and notifications.
Use when writing or reviewing Java unit tests. Enforces Mockito/JUnit 5 best practices - strict stubbing, no lenient mode, specific matchers, complete flow stubbing, Arrange-Act-Assert structure, and clear test naming.