Total 53,711 skills, Testing & QA has 1919 skills
Showing 12 of 1919 skills
Debug ESP32 firmware issues including compilation errors, runtime panics, memory issues, and communication failures
Unit testing patterns and best practices. Use when writing isolated unit tests, implementing AAA pattern, designing test isolation, or setting coverage targets for business logic.
Audit test coverage for code changes. Identifies untested logic and provides specific test recommendations. Read-only analysis. Use before PR or after implementation. Triggers: review coverage, check tests, test coverage, are tests adequate.
Router skill for choosing the right testing approach for Umbraco backoffice extensions
Combined command for OpenHarmony XTS compilation and execution. Complete the compilation and execution of XTS test projects in one stop. Use this Skill when you need to execute the full XTS test process: (1) Compile the XTS test project to generate HAP files, (2) Run the XTS test and display the results. Supports passing --package and --api parameters to the execution phase.
Manage Testany Workspaces - Member Management, Permission Configuration, Team Organization
Write Rails tests with RSpec, FactoryBot, and mocking patterns. Use when creating tests, writing specs for models/controllers/requests, setting up test fixtures, or mocking external services.
Zero Script QA - Testing methodology without test scripts. Uses structured JSON logging and real-time Docker monitoring for verification. Use proactively when user needs to verify features through log analysis instead of test scripts. Triggers: zero script qa, log-based testing, docker logs, 제로 스크립트 QA, ゼロスクリプトQA, 零脚本QA, QA sin scripts, pruebas basadas en logs, registros de docker, QA sans script, tests basés sur les logs, journaux docker, skriptloses QA, log-basiertes Testen, Docker-Logs, QA senza script, test basati sui log, log docker Do NOT use for: unit testing, static analysis, or projects without Docker setup.
Write and run unit tests for WoW addons using Busted and the Mechanic test framework. Covers test structure, mocking WoW APIs, and coverage analysis. Use when adding tests, fixing bugs with regression tests, or improving coverage. Triggers: test, unit test, coverage, Busted, mock, TDD, sandbox.
Step-by-step guide for writing focused, practical tests for Dust codebases following the 80/20 principle.
Apply London (mock-based) and Chicago (state-based) TDD schools. Use when practicing test-driven development or choosing testing style for your context.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first