testing

Standardize Ghost testing conventions with experimental fixtures and mock providers.

5|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/mrtolkien/GHOST --skill testing-mrtolkien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/mrtolkien/GHOST/tree/main/.agents/skills/testing
Command: npx skills add https://github.com/mrtolkien/GHOST --skill testing-mrtolkien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests and test infrastructure in the Ghost codebase suffer from inconsistent conventions, fragile fixtures, and hard-to-read harness code. This skill standardizes testing practices, defines reusable helpers, and codifies non-negotiable readability requirements to improve reliability and collaboration.

Core Features & Use Cases

  • Standardized test_config, test_workspace, test_database helpers for repeatable setup.
  • MockProvider and LiveTestEnv usage guidelines to run safe, isolated tests without touching user data.
  • Clear guidance for writing unit, integration, and live tests with deterministic fixtures and isolation guarantees.

Quick Start

Read this skill before writing or modifying any tests and apply the harness API and guidelines when adding or updating tests in the Ghost repository.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I standardize unit and integration tests in the Ghost codebase?

To standardize Ghost unit and integration tests, apply reusable test_config, test_workspace, and test_database helpers. This ensures repeatable setup, fixture isolation, and consistent readability across the entire test harness.

What is the best way to isolate live tests from user data in Ghost?

The best way to isolate live tests is by using MockProvider and LiveTestEnv usage guidelines. These standardized harness components run safe, isolated tests without touching real user data or database state.

Why are my Ghost test fixtures fragile and hard to read?

Ghost test fixtures become fragile and hard to read due to inconsistent conventions and unstandardized harness code. Applying experimental fixtures, mock providers, and non-negotiable readability rules solves this reliability issue.

How do I set up a repeatable test workspace for Ghost integration tests?

Set up a repeatable Ghost integration test workspace by utilizing the standardized test_workspace and test_database helpers. These helpers enforce deterministic fixtures and guarantee isolation for reliable integration testing.

Do I need mock providers for Ghost unit tests?

Yes, using MockProvider is recommended for Ghost unit tests to ensure safe, isolated execution. It enforces deterministic fixtures and prevents tests from touching user data or relying on external state.