fixtures

Create deterministic input fixtures for rendering, parsing, and I/O tests.

2.6k|145|Updated Feb 13, 2021
One-click install
npx skills add https://github.com/gridaco/grida --skill fixtures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixtures
Source: https://github.com/gridaco/grida/tree/main/.agents/skills/fixtures
Command: npx skills add https://github.com/gridaco/grida --skill fixtures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixtures provide static input files such as HTML, SVG, CSS, JSON, .grida, .fig, font binaries, images, and text samples to support deterministic rendering, parsing, and I/O tests, ensuring reproducible results across environments.

Core Features & Use Cases

  • Deterministic inputs: Use pre-defined fixtures to reproduce rendering and parsing outcomes.
  • Regression coverage: Each fixture maps to a feature or edge case to validate changes.
  • Onboarding and cross-pipeline validation: New contributors can learn the repository surface and tests; fixtures are reused across unit, golden, and reftest pipelines.

Quick Start

Organize a new set of deterministic input fixtures under fixtures/ and reference them from tests.

Frequently Asked Questions about fixtures

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

FAQPage Schema
How do I organize test fixtures for deterministic rendering and parsing tests?

Organize deterministic test fixtures by placing static input files under a fixtures/ directory and referencing them directly from unit, integration, and cross-pipeline tests to ensure reproducible outcomes across environments.

What file formats can be used as test data for regression testing?

Test data fixtures support static input files including HTML, SVG, CSS, JSON, .grida, .fig, font binaries, images, and text samples to validate specific features and edge cases across rendering pipelines.

How do I structure self-contained test fixtures without external dependencies?

Structure self-contained test fixtures by ensuring each file is properly named, maps to a specific feature or edge case, and is linked directly in tests without requiring external dependencies or network calls.

Can I use the same test fixtures across unit, golden, and reftest pipelines?

Yes, the same test fixtures can be reused across unit, golden, and reftest pipelines. This cross-pipeline validation ensures consistent I/O testing and helps new contributors learn the repository surface.

What's the best way to manage test data for onboarding new contributors to a repository?

Manage test data by organizing comprehensive, properly named fixtures that map to features. New contributors can learn the repository surface and expected behaviors by examining these deterministic inputs and their corresponding tests.

Why do my rendering tests produce different results across environments?

Rendering tests produce inconsistent results when they lack deterministic inputs. Supplying self-contained static fixtures ensures reproducible parsing and I/O validation outcomes across different testing environments.