test-setup

Automate test infrastructure and CI/CD setup for Godot, Unity, or Unreal projects.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill test-setup-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-setup
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/test-setup
Command: npx skills add https://github.com/MichaelSolati/mkai --skill test-setup-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up automated testing infrastructure and CI/CD pipelines for game development projects is time-consuming, error-prone, and often inconsistent across team members, especially when adhering to engine-specific best practices for tools like GdUnit4, Unity Test Framework, or Unreal Automation Testing.

Core Features & Use Cases

  • Multi-Engine Support: Auto-detects the configured game engine (Godot, Unity, Unreal Engine) and generates engine-specific test runner configurations and directory structures.
  • CI/CD Automation: Creates a ready-to-use GitHub Actions workflow that runs tests on every push to main and pull request, blocking merges on test failures.
  • Standardized Test Layout: Generates a consistent tests/ directory with unit, integration, smoke, and evidence subdirectories, plus seed files for smoke tests and test naming conventions.
  • Use Case: A game dev team can set up their entire testing pipeline in 5 minutes before their first sprint, eliminating hours of manual configuration and ensuring all team members follow the same testing standards.

Quick Start

Use the test-setup skill to scaffold the full testing infrastructure and CI workflow for your configured game engine project.

Frequently Asked Questions about test-setup

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

FAQPage Schema
How do I set up automated testing and CI pipelines for a Unity project?

To set up automated testing and CI pipelines for a Unity project, you can generate Unity Test Framework configurations, standardized test directories, and GitHub Actions workflows that block merges on test failures.

Does this test setup support Unreal Engine and Godot in addition to Unity?

Yes, the test setup supports Unreal Engine and Godot alongside Unity by auto-detecting the configured engine and generating engine-specific test runner configurations like Unreal Automation Testing and GdUnit4.

How do I create a standardized test directory layout for game development?

You can create a standardized test directory layout for game development by generating a tests directory with unit, integration, smoke, and evidence subdirectories, plus seed files and test naming conventions.

Can I block pull request merges automatically when game tests fail?

Yes, you can block pull request merges automatically when game tests fail by implementing a generated GitHub Actions workflow that executes test suites on every push to main and pull request.

What is the best way to scaffold smoke test templates before a game development sprint?

The best way to scaffold smoke test templates before a game development sprint is to automate the generation of pre-sprint testing infrastructure, which includes seed files for smoke tests and CI configuration.

Why does manual CI configuration for game testing often lead to errors?

Manual CI configuration for game testing often leads to errors and inconsistencies across team members because it requires adhering to engine-specific best practices for tools like GdUnit4, Unity Test Framework, and Unreal Automation Testing.