/v2-generate-pytest

Generate executable pytest files from Software Test Plan markdown documents.

Updated May 9, 2026

Search Tags:#automation #testing #pytest #python #sdlc #openshift

Ready to run

npx skills add https://github.com/Ruclo/thesis-artifact --skill v2-generate-pytest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: /v2-generate-pytest
Source: https://github.com/Ruclo/thesis-artifact/tree/main/v2/skills/v2-generate-pytest
Command: npx skills add https://github.com/Ruclo/thesis-artifact --skill v2-generate-pytest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges the gap between high-level Software Test Plans (STP) and technical implementation by automating the creation of boilerplate-heavy pytest files.

Core Features & Use Cases

Automated Test Mapping: Converts test scenarios and acceptance criteria from markdown STPs into structured Python test functions.
Context-Aware Generation: Leverages repository-specific utilities, fixtures, and conventions discovered during exploration to ensure generated code is immediately functional.
Use Case: When a new feature is defined in an STP, use this skill to generate the corresponding test suite, ensuring all imports and class signatures align perfectly with the existing codebase.

Quick Start

Invoke the generate pytest skill by providing the path to your software test plan markdown file.

Frequently Asked Questions about /v2-generate-pytest

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

FAQPage Schema

How do I generate pytest code from a markdown test plan?▼

You generate pytest code from a markdown test plan by providing the file path to the generation skill. It maps natural language test scenarios and acceptance criteria into structured, executable Python test functions.

Can I automatically map acceptance criteria to existing pytest fixtures and utilities?▼

Yes, automated test mapping converts acceptance criteria into structured Python test functions. It leverages repository-specific utilities and fixtures discovered during exploration to ensure the generated code is immediately functional.

How do I create pytest files that match my repository's existing import conventions?▼

To create pytest files that match existing import conventions, the generation process analyzes your codebase context. This ensures all imports and class signatures align perfectly with established architectural patterns before code generation.

Does this pytest generation approach work within the openshift-virtualization-tests environment?▼

Yes, this approach is specifically designed for the openshift-virtualization-tests environment. It facilitates the transition from natural language requirements to automated test code while adhering to the repository's strict architectural patterns.

What is the best way to automate boilerplate-heavy pytest file creation from Software Test Plans?▼

The best way to automate boilerplate-heavy pytest file creation is translating Software Test Plan markdown documents into executable code. This bridges the gap between high-level requirements and technical implementation by automating boilerplate generation.