What is a typical debugging strategy for failing generator tests?

• A. Run tests with verbose output, inspect generated files, and isolate failing prompts or writes
• B. Increase timeouts and retry automatically
• C. Ignore failing tests and proceed
• D. Only test successful runs

Answer: (A)

When debugging failing generator tests, reveal exactly what happened and where by first turning on verbose output so you get detailed logs, stack traces, and clear feedback about each step the generator takes. Then inspect what the generator wrote to disk in the temporary test directory—the generated files and their contents—to see if templates, paths, or content are off. Finally, narrow the failure to a specific part by running the test with a pared-down scenario: feed prompts one at a time or reduce the generator to a minimal sequence of writes and re-run until you pinpoint which prompt or write triggers the problem. This approach makes the error reproducible and actionable, guiding you to fix the underlying issue in prompts, templates, or file-generation logic. Increasing timeouts or retries can mask real problems, and skipping failing tests ignores the root cause.