microshift-dev:generate-tests

Generate Robot Framework test cases from Jira OCPSTRAT tickets.

7|15|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-dev-generate-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microshift-dev:generate-tests
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/microshift-dev/skills/generate-tests
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-dev-generate-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of designing comprehensive Robot Framework test coverage by deriving test scenarios directly from Jira OCPSTRAT tickets.

Core Features & Use Cases

  • Jira-to-test case generation: Fetches an OCPSTRAT ticket, extracts description/acceptance criteria, and identifies linked implementation context.
  • Coverage-aware planning: Reviews linked GitHub PRs to detect existing *.robot coverage and focuses only on the biggest gaps.
  • Robot Framework test creation workflow: Produces a test-case markdown doc plus the most critical Robot test file(s) following MicroShift conventions, with a controlled branch-and-file creation process.

Quick Start

Run /microshift-dev:generate-tests with your OCPSTRAT Jira ticket ID to generate a prioritized set of missing Robot Framework tests for the described MicroShift feature.

Frequently Asked Questions about microshift-dev:generate-tests

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

FAQPage Schema
How do I generate Robot Framework tests from a Jira ticket for MicroShift?▼

You can generate Robot Framework tests from a Jira OCPSTRAT ticket by providing the ticket ID. The tool fetches ticket details, analyzes linked PRs for existing coverage, and produces prioritized missing Robot test files.

What is the process for checking existing test coverage before creating new Robot tests?▼

Checking existing Robot test coverage involves inspecting linked GitHub PRs and scanning current *.robot files. This identifies already covered scenarios so generation focuses only on the biggest missing test gaps.

Can I use this to automate test creation for OpenShift features from acceptance criteria?▼

Yes, you can automate test creation for OpenShift features by extracting acceptance criteria from Jira tickets. It generates a test-case markdown document and critical Robot test files following MicroShift conventions.

How do I handle insufficient ticket details when generating Robot test cases?▼

When Jira ticket details are insufficient for test generation, the tool validates input sufficiency and triggers a user fallback path. This guided process ensures you provide necessary context before continuing.

Does the generated Robot test creation workflow follow MicroShift branch and file naming conventions?▼

Yes, the workflow follows MicroShift conventions by enforcing deterministic file naming and guided branch creation. It also ensures teardown-safe test authoring to maintain repository stability.

What are the limitations of automating Robot test generation from OCPSTRAT tickets?▼

Automation is limited to analyzing OCPSTRAT tickets, linked USHIFT tickets, and GitHub PRs. It requires sufficient Jira ticket details and valid web fetching access to determine missing test coverage accurately.