vss-test-coverage

Codify end-to-end test flows for API, UI, and infrastructure in the VSS stack.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates and codifies end-to-end testing for the Video Search and Summarization (VSS) stack, enabling repeatable, evidence-backed validation across API, UI, and infrastructure.

Core Features & Use Cases

  • Provides a comprehensive test plan skeleton for API, UI, and infra tests, with clear execution order and expected outcomes.
  • Supports smoke, regression, and long-running end-to-end test scenarios, with explicit preconditions and timeouts.
  • Serves QA engineers and developers by generating reproducible test artifacts and traceable results for deployed VSS stacks.

Quick Start

Run the VSS test coverage workflow against a deployed stack and follow the execution order to collect test evidence

Frequently Asked Questions about vss-test-coverage

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

FAQPage Schema
How do I automate end-to-end test coverage for a deployed Video Search and Summarization stack?

Automate end-to-end test coverage by codifying test flows for API, UI, and infrastructure resources. This enforces structured test definitions, explicit preconditions, and teardown semantics to ensure deterministic execution and reproducible failure reports.

What is the best way to run regression checks across API endpoints and UI components?

Run regression checks by applying structured test definitions to deployed stacks across API endpoints and UI components. This process generates reproducible test artifacts and collects traceable evidence for your test execution.

Can I execute long-running end-to-end test scenarios with explicit timeouts?

Yes, you can execute long-running end-to-end test scenarios with explicit preconditions and timeouts. The structured test definitions ensure deterministic execution and evidence collection throughout the long-running test flows.

Does this testing approach support smoke tests for infrastructure resources?

Yes, this testing approach supports smoke tests for infrastructure resources alongside API and UI components. It codifies test flows with clear execution order and expected outcomes to validate deployed stacks.

Why do I need explicit preconditions and teardown semantics for test execution?

Explicit preconditions and teardown semantics are needed to ensure deterministic execution and reproducible failure reports. They enforce structured test definitions that enable evidence-backed validation across API, UI, and infrastructure layers.