What practice enhances testability by reducing prompt friction in a generator?

• A. Provide defaults and sensible prompts to reduce friction
• B. Increase the number of prompts
• C. Remove prompts entirely
• D. Always revisit prompts for each run

Answer: (B)

Reducing prompt friction helps testability by making automated runs smooth and predictable. In a generator, prompts are questions you ask the user to configure the output. If every run requires manual answers, tests must pause or simulate input, which complicates automation and slows feedback. Providing defaults means the generator can run non-interactively, so tests can complete without hanging on prompts. Pairing defaults with sensible prompts keeps the tool usable for real users in interactive mode, while still allowing automation to proceed quickly during tests.

If you increase the number of prompts, you add more opportunities for a test to stall or for scripts to fail because input isn’t supplied, which hurts testability. Removing prompts altogether can remove configurability and lead to unusable defaults for real users, though it does remove friction; it sacrifices flexibility. Revisit prompts every run adds unnecessary repetition and slows automated workflows.

So the best practice is to provide defaults and sensible prompts to reduce friction while preserving usable interactivity, enhancing testability and automation.