What is the recommended approach to test a generator in isolation without touching the user's filesystem?

• A. Use yeoman-test to run the generator in a temporary directory and assert outputs without affecting real files
• B. Run tests inside the user's project directory
• C. Disable filesystem isolation
• D. Use yeoman-test with a persistent directory

Answer: (D)

Isolating tests for a Yeoman generator means running the generator in a clean, disposable space so nothing on the real filesystem is touched. The recommended approach is to execute the generator inside a temporary directory. Yeoman-test provides this capability (often via a pattern that creates a fresh temp folder for each test) so you can verify what would be created without touching the user’s actual project. After the test completes, the temporary directory is discarded, keeping the filesystem clean and the tests repeatable.

Why this fits best: it guarantees true isolation, letting you seed prompts and validate outputs in a controlled environment without any risk to real files or existing projects.

Why the other options don’t fit: testing inside the user’s project directory would alter real files and fail to provide isolation; disabling filesystem isolation defeats the purpose of isolation; using a persistent directory would retain state across tests, leading to flaky tests and unintended side effects.