skills.rest
heygen-com
heygen-comOFFICIAL
Explore all skills by this author →
GitHub

e2e-cli-test

Automate end-to-end HeyGen CLI validation against the live API in CI environments.

109|14|Updated Mar 30, 2026
Search Tags:#automation#integration#qa#ci-cd#e2e-testing#cli-testing#heygen-cli
One-click install
npx skills add https://github.com/heygen-com/heygen-cli --skill e2e-cli-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-cli-test
Source: https://github.com/heygen-com/heygen-cli/tree/main/.claude/skills/e2e-cli-test
Command: npx skills add https://github.com/heygen-com/heygen-cli --skill e2e-cli-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end validation of the HeyGen CLI against the live API to catch regressions before releases by exercising authentication, listing, detail retrieval, schema introspection, error handling, and the end-to-end write path.

Core Features & Use Cases

  • End-to-end validation of major CLI flows against the live API to ensure reliability in release cycles.
  • Deterministic test execution suitable for CI/CD environments with clear pass/fail signals.
  • Guards against regressions by validating auth, list/get, --human output, schema introspection, error handling, and the write path.

Quick Start

Run make test-e2e in the repository root to execute the end-to-end HeyGen CLI tests against the live API.

Frequently Asked Questions about e2e-cli-test

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

FAQPage Schema
How do I automate end-to-end CLI testing against a live API in CI?▼

Automate end-to-end CLI testing against a live API in CI by running make test-e2e in the repository root. This enforces deterministic execution and validates major HeyGen CLI workflows to catch regressions before releases.

What CLI workflows are covered in HeyGen end-to-end validation?▼

End-to-end validation covers authentication, listing, detail retrieval, schema introspection, error handling, and the write-path workflow. These major HeyGen CLI flows are exercised against the live API to ensure release reliability.

Do I need a built binary and API key to run e2e CLI tests?▼

Yes, running e2e CLI tests requires specific prerequisites including a built binary, a valid API key, and the correct repository layout. These ensure safe test isolation and deterministic execution against the live API.

What is the best way to catch HeyGen CLI regressions before release?▼

The best way to catch HeyGen CLI regressions before release is executing deterministic end-to-end validation against the live API. This approach tests authentication, schema introspection, and write paths with clear pass/fail signals for CI environments.

Why does my HeyGen CLI e2e test require safe isolation in CI environments?▼

HeyGen CLI e2e tests require safe isolation in CI environments to enforce deterministic execution and prevent side effects during write-path workflows. This ensures clear pass/fail signals when validating against the live API.

Related Skills

Explore More Software Engineering Skills→
nathanvalenathanvale
2

bun-runtime

Manage Bun runtime workflows for monorepos with bunx and bun.lockb.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

regression-test-generator

Generate regression tests from bug reports and detected test frameworks.

Community
Advanced
ynotradioynotradio

agent-automation-infrastructure

Document CI/CD automation infrastructure with Docker images and optimization strategies.

Official
Intermediate
eliottbusinesseliottbusiness

test-skill

Automate execution of predefined test scripts for regression testing.

Community
Basic