agentsclimarketplace

Test suite validation

Skill HolobiomicsLab/asb-skill-collections/collections/metabolomics/v2/skills/test-suite-validation

Curated, evidence-grounded skill and software-tool collections for scientific AI agents, generated by the AgenticScienceBuilder

Install
npx -y skills add HolobiomicsLab/asb-skill-collections --skill test-suite-validation

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

One thing to look at

  • 14 stars14 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 author says it does

Copied from the file, not written here

Use when after rewriting, refactoring, or updating a core computational module (e.g., calculate_feature_overlap.py in FERMO 0.8.7) to confirm that all existing unit tests pass with zero failures and that the rewritten code does not introduce regressions or break existing contracts.

The file declares its own license as CC-BY-4.0. 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

6.3 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

test-suite-validation

Summary

Execute a project's pytest test suite against a rewritten or refactored module to verify functional correctness and regression absence. This skill validates that implementation changes preserve expected behavior by running the full test harness with verbose diagnostics.

When to use

After rewriting, refactoring, or updating a core computational module (e.g., calculate_feature_overlap.py in FERMO 0.8.7) to confirm that all existing unit tests pass with zero failures and that the rewritten code does not introduce regressions or break existing contracts.

When NOT to use

  • The module has no existing unit tests or the test suite does not cover the rewritten code paths.
  • The rewritten implementation intentionally changes the module's public API or contract, requiring test suite updates before validation can pass.
  • pytest dependencies or the test environment are unavailable or incompatible with the target Python version.

Inputs

  • rewritten or refactored Python module (e.g., calculate_feature_overlap.py)
  • pytest test suite file(s) targeting the module
  • project configuration (pyproject.toml, setup.py, or requirements.txt) specifying dependencies
  • version-controlled repository snapshot (at the commit containing the rewritten implementation)

Outputs

  • pytest exit code (0 = all tests pass, non-zero = failures detected)
  • verbose test execution report with individual test outcomes
  • assertion failure or error messages (if any)
  • test coverage summary and pass/fail counts

How to apply

Clone or access the repository containing the rewritten module at the target version. Install pytest and all project dependencies specified in the requirements or setup configuration (e.g., pyproject.toml, setup.py, or requirements.txt). Locate and execute the pytest test suite targeting the rewritten module using pytest with verbose output (-v flag) to capture detailed test results and failure messages. Verify that all tests pass with exit code 0, that no assertion failures or errors are reported, and that the test coverage reflects the module's public API and edge cases. The verbose output provides traceability for any failures and confirms which test cases validated the implementation.

Related tools

Examples

pytest fermo_gui/tests/test_calculate_feature_overlap.py -v

Evaluation signals

  • pytest exit code is 0 with no assertion failures or errors reported.
  • Verbose output shows 100% test pass rate with all individual test cases listed as PASSED.
  • No exceptions, traceback messages, or timeout errors appear in test execution logs.
  • Test execution completes without skipped or xfail (expected fail) tests that were previously passing.
  • Test coverage metrics (if generated) confirm that critical code paths in the rewritten module are exercised by the passing tests.

Limitations

  • Test suite validation confirms only that existing tests pass; it does not guarantee absence of bugs in untested code paths or edge cases not covered by the original test suite.
  • Test suite must be maintained and kept in sync with the rewritten module's API; if the rewrite intentionally changes behavior, tests must be updated first.
  • Exit code 0 and passing tests do not verify performance characteristics, memory usage, or compatibility with upstream or downstream modules that depend on the rewritten code.

Evidence

  • [other] Do the pytest tests for the calculate_feature_overlap.py module pass when executed against the rewritten implementation in FERMO 0.8.7?: "Do the pytest tests for the calculate_feature_overlap.py module pass when executed against the rewritten implementation in FERMO 0.8.7?"
  • [other] Locate and execute the pytest test suite targeting calculate_feature_overlap.py using pytest with verbose output to capture test results. Verify that all tests pass with exit code 0 and no assertion failures or errors.: "Locate and execute the pytest test suite targeting calculate_feature_overlap.py using pytest with verbose output to capture test results. Verify that all tests pass with exit code 0 and no assertion"
  • [other] Clone or access the FERMO repository (fermo-metabolomics/FERMO) at the version containing the rewritten calculate_feature_overlap.py module. Install pytest and any dependencies listed in the project's requirements or setup configuration.: "Clone or access the FERMO repository (fermo-metabolomics/FERMO) at the version containing the rewritten calculate_feature_overlap.py module. Install pytest and any dependencies listed in the"
  • [readme] Dependencies including exact versions are specified in the pyproject.toml file.: "Dependencies including exact versions are specified in the pyproject.toml file."

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 328,083. 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.