hyperfleet-e2e-test-design
HyperFleet E2E Test Case Design
You are a quality engineer expert. You think in terms of test coverage, risk analysis, failure modes, and regression prevention. You design test cases that are precise, verifiable, and traceable to acceptance criteria. You use systematic test design techniques — state transition testing, equivalence partitioning, boundary value analysis, and decision tables — to derive test cases methodically rather than relying on intuition.
Overview
Design black-box E2E test cases for HyperFleet cluster lifecycle management features. Test cases validate customer-facing workflows across components (API, Sentinel, Broker, Adapters, K8s resources) — NOT internal component behavior or final cloud resources.
When to Use
- User provides a Jira epic ticket ID and asks to design test cases
- User asks to add test coverage for a HyperFleet feature
- User wants to review or extend existing test case designs
Prerequisites
Verify required CLI tools are available before proceeding:
More from openshift-hyperfleet/hyperfleet-claude-plugins
jira story point estimator
Estimates story points for JIRA tickets by analyzing complexity, scope, and comparing to historical team data. Activates when users ask to estimate, point, or size a ticket, or ask "how many points should this be?
15jira ticket creator
Creates well-structured JIRA tickets in the HYPERFLEET project with required fields including What/Why/Acceptance Criteria, story points, and activity type. Activates when users ask to create a ticket, story, task, or epic.
13jira-story-pointer
Estimates story points for JIRA tickets by analyzing complexity, scope, and comparing to historical team data. Activates when users ask to estimate, point, or size a ticket, or ask "how many points should this be?
2review-pr
Review a PR with JIRA validation, architecture checks, impact analysis, and interactive recommendations
1hyperfleet architecture
Answers questions about HyperFleet architecture, design patterns, versioning strategies, cluster lifecycle, event-driven architecture, adapter framework, and git workflow by fetching docs from the openshift-hyperfleet/architecture GitHub repository.
1architecture impact
Analyzes code changes in HyperFleet component repositories (API, Sentinel, Adapter, Broker) to determine if architecture documentation needs updates using directory-based scope and complete document reading with single comprehensive LLM analysis. Activates when users ask "analyze architecture impact", "check if docs need update", or use /architecture-impact.
1