How can you supply prompts programmatically in tests or automation?

• A. Use a separate test harness
• B. Cannot supply prompts programmatically
• C. Use yeoman-test's withPrompts (and withOptions) to supply answers
• D. Provide prompts via a mock API

Answer: (C)

In Yeoman testing, you feed answers to the generator’s prompts using the Yeoman Test helpers, specifically withPrompts (and you can pair it with withOptions). withPrompts supplies a map of prompt names to the answers you want the test to use, so the generator proceeds without waiting for real user input. The keys you provide should match the name fields of the prompts defined in the generator, and the values are the simulated responses. You can also pass CLI-style options via withOptions (for example, to skip installation steps) to keep tests fast and deterministic.

This approach makes tests repeatable and deterministic because you control exactly what the generator sees as input, enabling you to test different scenarios by varying the prompt answers. Other approaches like a separate test harness or a mock API aren’t the standard way to drive Yeoman prompts in tests; using withPrompts (and withOptions) is the built-in, supported method.