/v3-generate-pytest

Generate executable pytest code from Software Test Description markdown files.

Updated May 9, 2026
One-click install
npx skills add https://github.com/Ruclo/thesis-artifact --skill v3-generate-pytest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /v3-generate-pytest
Source: https://github.com/Ruclo/thesis-artifact/tree/main/v3/skills/v3-generate-pytest
Command: npx skills add https://github.com/Ruclo/thesis-artifact --skill v3-generate-pytest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill bridges the gap between natural language Software Test Descriptions (STD) and executable test automation, ensuring high fidelity to repository standards and preventing common implementation errors.

Core Features & Use Cases

  • Automated Test Generation: Translates test scenarios, preconditions, and acceptance criteria from Markdown STDs into structured Python pytest files.
  • Repository Context Awareness: Leverages discovered fixtures, imports, and naming conventions to ensure generated code is immediately runnable.
  • Error Prevention: Integrates GRAVEYARD.md findings to proactively avoid patterns that have caused previous test failures.

Quick Start

Run the v3-generate-pytest skill by providing the path to your target STD markdown file to generate the corresponding test suite.

Frequently Asked Questions about /v3-generate-pytest

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

FAQPage Schema
How do I generate pytest code from Software Test Description markdown files?

To generate pytest code from Software Test Description markdown files, you provide the path to the target STD file, which the skill parses to map scenarios and acceptance criteria into structured Python test files.

Can I use this to automate pytest generation for the openshift-virtualization-tests repository?

Yes, this skill operates within the openshift-virtualization-tests repository context to ensure generated pytest automation adheres to discovered repository-specific fixtures, imports, and naming conventions.

What is the best way to prevent common test automation failures when generating pytest code from STDs?

The best way to prevent common test automation failures is by integrating GRAVEYARD-documented failure patterns, which the skill proactively parses to avoid previous test implementation errors.

Does the generated pytest code require manual fixture mapping to be executable?

No, the generated pytest code does not require manual fixture mapping because the skill leverages discovered repository-specific fixtures and utilities to ensure the output is immediately runnable.

What input format is needed to convert test scenarios into executable pytest files?

The required input format is a markdown Software Test Description file containing preconditions, test scenarios, and acceptance criteria mapped to repository-specific utilities.

Why does automated test generation fail to match repository standards without context awareness?

Automated test generation fails to match repository standards without context awareness because it cannot automatically discover and apply the specific fixtures, imports, and naming conventions required for functional compliance.