Which practice helps ensure tests do not alter the user's real projects?

• A. Run the generator in a temporary directory during tests
• B. Always commit changes to the user's repository
• C. Disable cleanup after tests
• D. Manually copy files into the test suite

Answer: (A)

Isolating test runs by executing the generator in a temporary directory protects the user’s real project from any changes. A sandboxed workspace lets the test freely create, modify, and delete files as part of verification without touching the actual project, ensuring results are reliable and reproducible. After the test, the entire temporary directory can be discarded, leaving no trace in the user’s environment and avoiding side effects on future tests.

Committing changes to the user’s repository would contaminate real work and create unwanted drift. Not cleaning up after tests leaves generated artifacts behind, cluttering the workspace and potentially interfering with other tests. Manually copying files into the test suite undermines true isolation and may not reflect how the generator behaves in a real project.