agentsclimarketplace
Sign in

Software testing guide

Skill RedlineTriad/skills/skills/software-testing-guide

Select, classify, audit, and implement proportionate software tests and verification. Use for test strategy, test portfolio design, gap analysis, terminology, CI quality gates, and choosing among unit, integration, E2E, property, fuzz, mutation, formal, performance, security, production, and human evaluation.From its SKILL.md

Install
npx -y skills add RedlineTriad/skills --skill software-testing-guide

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.5 KB, 399 tokens by cl100k_base, as published. Nobody here has run it

Software Testing Guide

Treat testing as evidence against concrete risks.

Method

  1. Inspect the change or system, public behavior, boundaries, existing tests, CI, and repository conventions.
  2. Identify consequential failure modes and stable observable seams.
  3. Choose the smallest credible portfolio: narrow deterministic checks for local behavior, real boundary checks for integration assumptions, and broad journeys for assembly risks.
  4. Implement proportionately, reuse existing tools, run relevant checks, and distinguish observed results from recommendations.

Load references/taxonomy.md for broad strategy or terminology. Load references/selection.md for portfolio selection, audits, and implementation planning.

Classification

Describe verification using the coordinates that add useful information:

mechanism × scope × target × purpose × technique × oracle × perspective × lifecycle × environment

Key distinctions:

  • unit/component/integration/system/E2E describe scope;
  • UI/API/CLI/database/protocol describe targets;
  • property/fuzz/snapshot/visual/differential/fault injection describe techniques or oracles;
  • security/performance/accessibility/reliability/compatibility describe purposes;
  • regression/smoke/acceptance/characterization describe intent;
  • black/white/grey box describe perspective;
  • static analysis, formal verification, human evaluation, online experiments, production verification, and mutation analysis describe mechanisms.

Preserve understandable repository terminology. Add qualifiers where they clarify evidence, such as integration/API contract, E2E/browser smoke, or unit/property.

Prefer checks with meaningful behavioral sensitivity, independent oracles, controlled nondeterminism, fast diagnosis, and complementary evidence. Use coverage, mutation results, failure history, and production signals to refine the portfolio.

Routine local and hermetic verification can proceed directly. Use a guided plan for production traffic, destructive recovery, expensive shared load, real-user research, penetration or red-team work, certification, and public contract changes.

What ships with it: 3 files

14.9 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.