testing-pack

Automate end-to-end OCI starter pack testing via ORM UI and agent-browser.

3|2|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill testing-pack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-pack
Source: https://github.com/oci-ai-incubations/ai-accelerator-starter-packs/tree/main/.claude/skills/testing-pack
Command: npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill testing-pack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires websocket-client, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Orchestrates end-to-end testing of OCI starter packs by automating the full lifecycle from infrastructure and application stacks to health checks and smoke tests, removing manual setup and validation steps.

Core Features & Use Cases

  • End-to-end orchestration of infra and app stacks using a two-stack model with agent-browser automation
  • Schema validation, zip creation, and phase-based deployment monitoring with actionable feedback
  • PR integration for evidence and test results with optional screenshot uploads to PRs

Quick Start

Initiate testing by asking me to test a starter pack (e.g., 'test this pack'), and I will run the full two-stack deployment, validation, and testing workflow.

Frequently Asked Questions about testing-pack

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

FAQPage Schema
How do I automate end-to-end testing for OCI starter packs?

Automate end-to-end testing for OCI starter packs by orchestrating infra and app stacks through the ORM UI using agent-browser. This workflow handles schema validation, zip creation, deployment, and post-deploy verification automatically.

What does two-stack deployment testing involve for infrastructure and application stacks?

Two-stack deployment testing orchestrates separate infrastructure and application stacks, applying schema validation and phase-based monitoring. It automates health checks and smoke tests to verify post-deploy stability without manual setup.

Can I post test evidence and screenshots directly to a pull request?

Yes, pull request integration posts test evidence and results directly to PRs. The workflow handles PR-number validation and optionally uploads screenshots to provide visual proof of the deployment and testing phases.

Do I need websocket-client to run starter pack testing orchestration?

Yes, websocket-client is a required dependency for agent-browser automation within the testing orchestration. It enables the real-time communication needed to drive the ORM UI during deployment and validation.

What guardrails are applied during starter pack deployment and region capacity checks?

Guardrails include validating starter_pack_size, performing region capacity checks, and handling PR numbers for evidence posting. Phase-based progress reporting provides actionable feedback throughout the deployment lifecycle.

Why use agent-browser automation for infrastructure and app stack validation?

Agent-browser automation drives the ORM UI to execute schema validation and deployment steps that normally require manual interaction. This removes repetitive setup, ensuring consistent post-deploy verification across starter packs.