fixture-testing

Simulate project trees with fixture helpers for llmview testing.

1|Updated Jan 25, 2026

Search Tags:#vitest #testing #filesystem #unit-tests #integration-tests #fixture #llmview

Ready to run

npx skills add https://github.com/noahtren/llmview --skill fixture-testing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fixture-testing
Source: https://github.com/noahtren/llmview/tree/main/skills/fixture-testing
Command: npx skills add https://github.com/noahtren/llmview --skill fixture-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixture-based testing of llmview requires reliable, repeatable environments that simulate real projects without polluting the workspace.

Core Features & Use Cases

In-memory trees built with file(relativePath, content) and dir(relativePath, children) to model project structures.
Disk-anchored testing via toDiskTmp and cleanupDisk to exercise end-to-end pipelines (scanDirectory, selectFiles, renderFiles, formatOutput, execute).
Guidance for reusable fixtures, test patterns, and coverage of unit and integration tests across core rendering rules.

Quick Start

Create an in-memory tree using file and dir helpers, then convert to a temporary on-disk path with toDiskTmp for end-to-end tests.

Frequently Asked Questions about fixture-testing

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

FAQPage Schema

How do I set up fixture-based testing for a filesystem without polluting my workspace?▼

Filesystem fixture testing uses in-memory trees built with file and dir helpers to simulate project structures, preventing workspace pollution. You can model complex directories safely and convert them to temporary disk paths only when needed for end-to-end execution.

How do I run end-to-end tests against temporary disk fixtures?▼

End-to-end tests run by converting in-memory trees to temporary disk paths using toDiskTmp, exercising pipelines like scanDirectory and renderFiles. After running your execute and formatOutput tests, you call cleanupDisk to safely remove the temporary disk fixtures.

What is the best way to structure unit and integration tests for rendering pipelines?▼

The best way to structure rendering pipeline tests is using reusable fixture helpers to verify rendering rules across unit and integration tests. This approach targets specific pipeline stages like selectFiles and formatOutput, ensuring reliable and repeatable test environments.

Does fixture testing work with both in-memory trees and temporary disk utilities?▼

Fixture testing works with both in-memory trees and temporary disk utilities. You can use in-memory structures for fast unit tests and toDiskTmp with cleanupDisk for integration and end-to-end tests that require actual disk anchoring.

Why should I use fixture helpers for testing project trees instead of real directories?▼

Fixture helpers provide reliable, repeatable testing environments that simulate real project trees without the risk of polluting your workspace. They allow precise control over file and directory structures, ensuring consistent test execution across rendering pipelines.