agentsclimarketplace

Opp repl feature and release tests

Skill tabgab/opp_repl-skill/opp-repl-feature-and-release-tests

Composable Anthropic-format Agent Skills for driving OMNeT++ simulations via opp_repl. Works in Claude, Windsurf, and any SKILL.md-aware agent.

Install
npx -y skills add tabgab/opp_repl-skill --skill opp-repl-feature-and-release-tests

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

2 things to look at

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

Copied from the file, not written here

Comprehensive test suites — feature tests verify builds with different optional feature combinations, release tests validate release candidates, and run_all_tests sequentially runs every configured test type. Load for release-gate CI pipelines that want one call to rule them all.

SKILL.md

2.9 KB, as published. Nobody here has run it

Feature, release, and all-tests suites

Three convenience entry points that sit above the specific test types (opp-repl-smoke-tests, opp-repl-fingerprint-tests, etc.).

Upstream reference: https://github.com/omnetpp/opp_repl/blob/main/doc/feature_tests.md

Feature tests

Check that the project builds and simulations set up correctly with each documented combination of optional features (OMNeT++ "features" as declared in .oppfeatures).

run_feature_tests(simulation_project=inet_project)

CLI:

opp_run_feature_tests --load inet.opp -p inet

Release tests

A curated suite suitable for validating a release build — combines smoke, fingerprint, statistical, feature, and chart tests (exact composition is project-defined).

run_release_tests(simulation_project=inet_project)

CLI:

opp_run_release_tests --load inet.opp -p inet

Run all tests

Sequentially run every configured test type:

run_all_tests(simulation_project=inet_project)

CLI:

opp_run_all_tests --load inet.opp -p inet

When to use which

  • run_smoke_tests() only -- fast feedback on feature branches.
  • run_feature_tests() -- before merging changes that touch build configuration, NED features, or optional modules.
  • run_release_tests() -- the official gate for pushing a release.
  • run_all_tests() -- use during maintenance or when you want a single verdict; overlap with run_release_tests() is intentional in many projects. When module-image tests are configured for the project, run_all_tests() includes them automatically (via run_module_image_tests()).
  • Module-image tests (opp-repl-module-image-tests) -- visual regression of module/network rendering; run independently with run_module_image_tests() / opp_run_module_image_tests CLI.

Pitfalls

  • These entry points aggregate long-running tests; expect tens of minutes to hours depending on project size. Pin sim_time_limit and use --no-concurrent sparingly.
  • Because each sub-suite has its own baselines, any ONE stale baseline can fail the whole aggregate. Fix baselines incrementally using the individual update_*_test_results entry points.
  • Results are reported per sub-suite, not merged into a single MultipleTaskResults. Inspect each section for drill-down.

See also

  • Every other opp-repl-*-tests skill.
  • opp-repl-module-image-tests — visual regression of module/network rendering (distinct from chart/analysis-plot tests).
  • opp-repl-tasks-and-results — per-sub-suite drill-down.
  • opp-repl-github-actions — dispatch suites remotely.

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.