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,153–1,176 of 30,722 skills

Testlab Integration Testing Api Compatibility Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: integration testing for API compatibility. Produce a failure-triage record and reversible recovery plan 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 failure is bounded by observations, one testable...testingrustgoVotes: 0GitHub stars: 2
Testlab Integration Testing Api Compatibility Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: integration testing for API compatibility. Produce a staged design blueprint 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 interfaces, dependencies, constraints, and review points are testable before build....testingrustgoVotes: 0GitHub stars: 2
Testlab Integration Testing Api Compatibility Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: integration testing for API compatibility. Produce a bounded build or configuration runbook 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 prepared result is reproducible, reviewable, and within ...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Version Migrations Verification And Acceptance Test PlanAUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: fuzz testing for version migrations. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Verify forward and recovery paths on disposable data, including compatibility and partial-failure behavior. Success means each critical requirement maps to a reproducible check and a truth...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Version Migrations 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: fuzz testing for version migrations. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Verify forward and recovery paths on disposable data, including compatibility and partial-failure behavior. Success means the proposed change is compared with a baseline, regres...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Test Isolation Verification And Acceptance Test PlanAUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: fuzz testing for test isolation. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means each critical requirement maps to a reproducible check an...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Test Isolation 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: fuzz testing for test isolation. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means the proposed change is compared with a baselin...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Release Candidates Verification And Acceptance Test PlanAUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: fuzz testing for release candidates. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means each critical requirement maps to a reproducible check and a tru...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Release Candidates 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: fuzz testing for release candidates. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means the proposed change is compared with a baseline, regr...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Regression Coverage Verification And Acceptance Test PlanAUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: fuzz testing for regression coverage. Produce a risk-weighted verification plan with saved evidence 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 each critical requirement maps to a reproducible check and a truthful pass, fai...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Regression Coverage Security Rights And Safety ReviewAUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software testing and release assurance: fuzz testing for regression coverage. Produce a scoped risk-and-control review 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 review names relevant hazards, permissions, controls, evidence gaps, and...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Regression Coverage Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Software testing and release assurance: fuzz testing for regression coverage. Produce a scope-and-baseline record 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 owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, preserve a baseline,...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Regression Coverage Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Software testing and release assurance: fuzz testing for regression coverage. Produce a reviewable requirements and decision brief 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 requirements have priorities, evidence, owners, and measurable acceptance conditions. Use perm...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Regression Coverage Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Software testing and release assurance: fuzz testing for regression coverage. Produce an evidence-backed option-comparison matrix 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 options are compared on user-approved criteria with uncertainty and trade-offs shown. Use permiss...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Regression Coverage 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: fuzz testing for regression coverage. Produce a versioned improvement proposal and handoff packet 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 proposed change is compared with a baseline, regression risk is ...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz 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: fuzz 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 next ste...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Regression Coverage Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: fuzz testing for regression coverage. Produce a staged design blueprint 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 interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preser...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz Testing Regression Coverage Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: fuzz 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 permissi...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz 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: fuzz 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 reproducible che...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz 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: fuzz 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 with a ba...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz 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: fuzz 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 pass, fa...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz 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: fuzz 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, regression risk is...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz 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: fuzz 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 check and a ...testingrustgoVotes: 0GitHub stars: 2
Testlab Fuzz 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: fuzz 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 baseline, r...testingrustgoVotes: 0GitHub stars: 2