opp-repl-feature-and-release-tests

Orchestrate opp_repl test suites and aggregate per-suite results for CI release gating.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tabgab/opp_repl-skill --skill opp-repl-feature-and-release-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opp-repl-feature-and-release-tests
Source: https://github.com/tabgab/opp_repl-skill/tree/main/opp-repl-feature-and-release-tests
Command: npx skills add https://github.com/tabgab/opp_repl-skill --skill opp-repl-feature-and-release-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and centralizes end-to-end testing for opp_repl projects, enabling teams to validate feature combinations and release readiness with a single interface.

Core Features & Use Cases

  • Run feature tests, release tests, and the all-tests suite to comprehensively validate builds.
  • Coordinate multiple sub-suites (e.g., smoke, fingerprint, etc.) and produce per-suite results that align with baselines.
  • Ideal for CI pipelines and pre-release checks to prevent regressions before merging.

Quick Start

Run all configured test types with run_all_tests(simulation_project=inet_project) to validate a release-ready build.

Frequently Asked Questions about opp-repl-feature-and-release-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end feature tests for CI release gating?

You can automate end-to-end feature tests for CI release gating by orchestrating multiple sub-suites through a single interface, validating feature combinations and build readiness with structured results.

What is the best way to run nightly validation across optional feature combinations?

Nightly validation across optional feature combinations is handled by coordinating various sub-suites like smoke and fingerprint tests, producing per-suite results that align with validation baselines.

Can I use a unified test suite for pre-merge checks and release candidates?

Yes, a unified test suite can be used for pre-merge checks and release candidates to prevent regressions before merging by comprehensively validating builds across multiple test types.

How do I aggregate multiple sub-suites to validate release readiness?

You aggregate multiple sub-suites to validate release readiness by running all configured test types together, which centralizes the validation process and provides structured results for each suite.

Does running all configured test types require manual test effort for build validation?

No, running all configured test types requires minimal manual test effort because the process automates and centralizes end-to-end testing, speeding up feedback for release candidates.