Testing & QA

Unit tests, integration tests, E2E, QA, validation, and test automation

skills in category: 30,722
pages available: 1,281

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse testing & qa skills

Showing 1,249–1,272 of 30,722 skills

Testlab Accessibility Testing Regression Coverage Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: accessibility testing for regression coverage. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means the failure is bounded by observations, one testable hypothesis, and a safe...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Regression Coverage Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: accessibility testing for regression coverage. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means the prepared result is reproducible, reviewable, and within the approved scope. Use...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Legacy Code Verification And Acceptance Test PlanAUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: accessibility testing for legacy code. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means each critical requirement maps to a reprodu...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Legacy Code Measured Improvement And HandoffAUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: accessibility testing for legacy code. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means the proposed change is compared ...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Flaky Failures Verification And Acceptance Test PlanAUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: accessibility testing for flaky failures. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means each critical requirement maps to a reproducible check and a truthful...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Flaky Failures Measured Improvement And HandoffAUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: accessibility testing for flaky failures. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means the proposed change is compared with a baseline, regressio...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Data Edge Cases Verification And Acceptance Test PlanAUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: accessibility testing for data edge cases. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means each critical requirement maps to a reproducible che...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Data Edge Cases Measured Improvement And HandoffAUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: accessibility testing for data edge cases. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means the proposed change is compared with a ba...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Cross Platform Behavior Verification And Acceptance Test PlanAUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means each critical requirement maps to a reproducible check and a...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Cross Platform Behavior Measured Improvement And HandoffAUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means the proposed change is compared with a baseline, ...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Ci Cost Budgets Verification And Acceptance Test PlanAUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: accessibility testing for CI cost budgets. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means each critical requirement maps to a reproducible check and ...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Ci Cost Budgets Measured Improvement And HandoffAUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: accessibility testing for CI cost budgets. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means the proposed change is compared with a baseline,...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Api Compatibility Verification And Acceptance Test PlanAUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: accessibility testing for API compatibility. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means each critical requirement maps to a reproduci...testingrustgoVotes: 0GitHub stars: 2
Testlab Accessibility Testing Api Compatibility Measured Improvement And HandoffAUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: accessibility testing for API compatibility. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means the proposed change is compared wi...testingrustgoVotes: 0GitHub stars: 2
Test Driven Development WorkflowAUse when implementing new behavior, fixing a defect, or refactoring code where automated checks can describe the expected behavior to turn acceptance criteria into focused tests, observe a meaningful failing test, make the smallest change that passes, then refactor and re-verify. Trigger for feature work, bug fixes, and behavior-changing refactors; adapt the test form when automation is not practical.testingrailsrefactoringVotes: 0GitHub stars: 2
Synthetic Upload Content ValidationAUse when a web workflow accepts user-selected files to create or update an upload boundary matrix with file metadata and observed outcomes. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: valid files are accepted and invalid or oversized files are rejected with safe feedback. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible wri...testingrustgoVotes: 0GitHub stars: 2
Requirement Row To Test Identifier Coverage AuditAUse when a requirements matrix has been revised before a release or implementation handoff to create or update a requirement-to-test map with uncovered rows and orphan tests. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: each required behavior has at least one relevant check and no check is falsely mapped. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before exter...testingrustgoVotes: 0GitHub stars: 2
Release Note Bullet To Change Set TraceAUse when a release note is prepared from a branch, tag, or pull-request set to create or update a release-note trace table with change links and audience impact. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: each bullet is supported by a merged or approved change and describes its effect accurately. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally v...testingrustgoVotes: 0GitHub stars: 2
Pull Request Test Failure Change AttributionAUse when a CI test fails after a branch update to create or update a failure-attribution note with base comparison and evidence. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the failure reproduces on the branch and is distinguishable from the base result. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible writes.testingrustgoVotes: 0GitHub stars: 2
Performance Benchmarking And Regression DetectionAUse when measuring application, service, build, or browser performance; investigating a slowdown; or comparing a change against a baseline to define representative workloads, environmental controls, metrics, and acceptable variance before optimizing. Trigger for performance investigations and regression gates, not speculative micro-optimization.testinggorailsVotes: 0GitHub stars: 2
Minimal Test Reproducer SculptorAUse when a large fixture, request, or state sequence obscures a test defect to create or update a minimized reproduction and a record of removed dimensions. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the reduced case still fails for the same reason and the original case remains available. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible o...testingrustgoVotes: 0GitHub stars: 2
Macos Update Payload Signature Negative TestAUse when a task involves testing that a macOS app update client rejects altered or incorrectly signed update payloads to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.testingswiftrailsVotes: 0GitHub stars: 2
Macos Notarization Ticket Stapling VerificationAUse when a task involves verifying that a notarization ticket is attached to the intended macOS artifact to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.testingswiftrailsVotes: 0GitHub stars: 2
Json Output Schema Roundtrip Invariant TestAUse when an agent or service emits JSON consumed by another component to create or update a round-trip fixture set with invariant results. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: normalized input and output preserve required fields and meanings. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible writes.testingrustgoVotes: 0GitHub stars: 2