Index of every page on this site: llms.txt
All skills
a2ui-project avatar

/a2ui-test-quality-check

@6bf4cc2
by A2UIa2ui-project/a2ui18k stars
1,430
Run it yourself

Auditing test suites for assertion utility, boundary cases coverage, and verification strength.

Use this Skill: https://skilld.dev/gh/a2ui-project/a2ui/a2ui-test-quality-check

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈30 tokens for metadata: the name and description. ≈582 when used: this file.

Description uses 1.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈121 characters, or 1.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

A2UI Test Quality & Assertions Auditing Skill

This skill guides you through the process of auditing codebase test suites to verify that tests are providing robust, meaningful assertions and verifying critical invariants, rather than simply running paths for code coverage.


Instructions

  1. Locate Test Suites:

    • Find all test directories and test files in each platform's implementation folder (e.g. tests/, test/, *Tests.swift).
  2. Audit Assertion Quality:

    • For each test case, inspect the assertions used:
      • Flag "weak assertions" that only verify non-null or truthy values without checking specific payload structure, field values, or types (e.g. expect(result).not.toBeNull() on a complex object).
      • Flag "empty tests" that execute code blocks but lack any assertions or mocks verifications (e.g. executing to check for lack of exceptions, unless it is explicitly marked as a no-throw smoke test).
      • Ensure that return models, state side effects, and events dispatched have corresponding value-matching assertions.
  3. Audit Behavioral and Boundary Coverage:

    • Review if tests exist for typical logical edge cases:
      • Null, empty, or overflow values.
      • Invalid JSON or parsing errors (e.g., throwing correct exceptions).
      • Exception propagation and error boundaries.
      • Timeout handling and cleanup side effects.
    • Look for cases where tests might pass when they should fail.
    • Cross-reference with the codebase's main files: if a file has complex parsing/validation code, ensure there are dedicated failing test cases asserting that errors are reported correctly.
  4. Audit Mocking Realism:

    • Ensure mocks and stubs verify their call parameters (e.g., verifying that a mock transport received the exact payload sent by the SDK, rather than just asserting it was called).
  5. Format the Report:

    • Build a Markdown report summarizing the findings:
      • Table of audited test suites and files.
      • Weak Assertions: List of test cases that rely on weak or missing assertions.
      • Missing Edge Case Tests: Critical logic boundaries and exception paths lacking tests.
      • Mocking Mismatches: Mock implementations that fail to verify call structures.
    • Return this Markdown report as your final response.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    This skill is designed to audit codebase test suites for assertion quality and coverage. While the skill's logic is functional and serves a legitimate development purpose, it possesses a low-severity attack surface for indirect prompt injection because it processes untrusted source code from the local filesystem.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: MEDIUM · 1 issue

Signed by skilld at 6bf4cc2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
metadata
{
  "internal": true
}

README badge

README badge for a2ui-project/a2ui/a2ui-test-quality-check