All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 31,094
- 1,296
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 browserBrowse testing & qa skills
Showing 1,777–1,800 of 31,094 skills
- Kubernetes Externaltrafficpolicy Client Ip Behavior TestUse when a task involves testing how Service external traffic policy affects source IP preservation and node-level routing to record Kubernetes server and client versions, cluster distribution and provider, API versions, namespace and workload owner, data sensitivity, evidence requirements, and maintenance window. Check current Kubernetes and provider documentation, begin with read-only evidence, and validate changes in an approved environment. Do not modify production resources, credentials,...Votes: 0GitHub stars: 2
- Kubernetes Dns Egress Allowlist Impact TestUse when a task involves testing whether restrictive egress rules preserve required cluster DNS resolution to record Kubernetes server and client versions, cluster distribution and provider, API versions, namespace and workload owner, data sensitivity, evidence requirements, and maintenance window. Check current Kubernetes and provider documentation, begin with read-only evidence, and validate changes in an approved environment. Do not modify production resources, credentials, or persistent d...Votes: 0GitHub stars: 2
- Kubernetes Default Deny Networkpolicy Coverage AuditUse when a task involves checking whether namespaces and workloads are covered by intended ingress and egress isolation to record Kubernetes server and client versions, cluster distribution and provider, API versions, namespace and workload owner, data sensitivity, evidence requirements, and maintenance window. Check current Kubernetes and provider documentation, begin with read-only evidence, and validate changes in an approved environment. Do not modify production resources, credentials, or...Votes: 0GitHub stars: 2
- Kubernetes Daemonset Node Coverage ReconciliationUse when a task involves checking that required node-level agents run on every eligible node and only intended nodes to record Kubernetes server and client versions, cluster distribution and provider, API versions, namespace and workload owner, data sensitivity, evidence requirements, and maintenance window. Check current Kubernetes and provider documentation, begin with read-only evidence, and validate changes in an approved environment. Do not modify production resources, credentials, or pe...Votes: 0GitHub stars: 2
- Kubernetes Custom Metric Freshness Scaling TestUse when a task involves testing that a custom or external metric is fresh and correctly scoped before it drives scaling to record Kubernetes server and client versions, cluster distribution and provider, API versions, namespace and workload owner, data sensitivity, evidence requirements, and maintenance window. Check current Kubernetes and provider documentation, begin with read-only evidence, and validate changes in an approved environment. Do not modify production resources, credentials, o...Votes: 0GitHub stars: 2
- Kubernetes Crd Schema Conversion Upgrade TestUse when a task involves testing custom-resource schema and conversion behavior across an operator upgrade to record Kubernetes server and client versions, cluster distribution and provider, API versions, namespace and workload owner, data sensitivity, evidence requirements, and maintenance window. Check current Kubernetes and provider documentation, begin with read-only evidence, and validate changes in an approved environment. Do not modify production resources, credentials, or persistent d...Votes: 0GitHub stars: 2
- Kubernetes Configmap Projection Reload Behavior TestUse when a task involves testing whether a workload observes ConfigMap updates through mounted files or environment values to record Kubernetes server and client versions, cluster distribution and provider, API versions, namespace and workload owner, data sensitivity, evidence requirements, and maintenance window. Check current Kubernetes and provider documentation, begin with read-only evidence, and validate changes in an approved environment. Do not modify production resources, credentials,...Votes: 0GitHub stars: 2
- Kubernetes Cloud Metadata Egress Isolation TestUse when a task involves testing whether Pods can reach a cloud metadata endpoint they should not use to record Kubernetes server and client versions, cluster distribution and provider, API versions, namespace and workload owner, data sensitivity, evidence requirements, and maintenance window. Check current Kubernetes and provider documentation, begin with read-only evidence, and validate changes in an approved environment. Do not modify production resources, credentials, or persistent data w...Votes: 0GitHub stars: 2
- Kubernetes Apiserver Load Balancer Failover TestUse when a task involves testing API-server endpoint continuity when one control-plane backend becomes unavailable to record Kubernetes server and client versions, cluster distribution and provider, API versions, namespace and workload owner, data sensitivity, evidence requirements, and maintenance window. Check current Kubernetes and provider documentation, begin with read-only evidence, and validate changes in an approved environment. Do not modify production resources, credentials, or pers...Votes: 0GitHub stars: 2
- Docker Agent Deployment ReadinessUse when a task involves preparing a Docker Agent for serving, registry distribution, or CI evaluation without deploying it prematurely to identify the intended outcome, affected account or artifact, exact product version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive details, produce a reviewable result, and verify it against explicit criteria. Trigger for planning, configuration, implementation, or troubleshooting in this focu...Votes: 0GitHub stars: 2
- Container Assurance Attestation Binding Scenario Sensitivity MatrixUse when the container attestation subject binding team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the attestation verification worksheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the statement verifies against the exact artifact and expected policy, without treating signature presence alone as trust. Use configured...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Log Coverage Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Authorized cybersecurity testing and defense: web application defense for log coverage. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means each critical requirement maps to a reproducibl...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Log Coverage Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: web application defense for log coverage. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissio...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Log Coverage Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: web application defense for log coverage. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means requirements have priorities, evidence, owners, and measurable...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Log Coverage Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: web application defense for log coverage. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means options are compared on user-approved criteria with uncertainty a...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Log Coverage Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: web application defense for log coverage. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means the failure is bounded by observations, one testable...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Log Coverage Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: web application defense for log coverage. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means interfaces, dependencies, constraints, and review points are testable before build....Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Log Coverage Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Authorized cybersecurity testing and defense: web application defense for log coverage. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means the prepared result is reproducible, reviewable, and within ...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Control Coverage Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Authorized cybersecurity testing and defense: web application defense for control coverage. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means each critical requirement maps to a reproducible che...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Control Coverage Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: web application defense for control coverage. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned i...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Control Coverage Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: web application defense for control coverage. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means requirements have priorities, evidence, owners, and measurable acce...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Control Coverage Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: web application defense for control coverage. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means options are compared on user-approved criteria with uncertainty and tr...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Control Coverage Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: web application defense for control coverage. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means the failure is bounded by observations, one testable hypo...Votes: 0GitHub stars: 2
- Authorizedsec Web Application Defense Control Coverage Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: web application defense for control coverage. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means interfaces, dependencies, constraints, and review points are testable before build. Use ...Votes: 0GitHub stars: 2