Is your feature request related to a problem?
Users may want to see what tests would be generated by the tool without actually modifying any files. This allows for a safe preview of the tool's output.
Describe the solution you'd like
Add a --dry-run flag to the main command. When this flag is present, the tool should perform all steps of the test generation process (coverage analysis, code chunking, AI calls) but instead of writing the results to files, it should print the generated tests to the console.
The output should clearly indicate which file each generated test belongs to.
Describe alternatives you've considered
- An interactive mode (provides more control but is not a simple preview).
- Generating tests and then having the user revert them with
git (clunky workflow).
Additional context
This is from the New Ideas Backlog.
Is your feature request related to a problem?
Users may want to see what tests would be generated by the tool without actually modifying any files. This allows for a safe preview of the tool's output.
Describe the solution you'd like
Add a
--dry-runflag to the main command. When this flag is present, the tool should perform all steps of the test generation process (coverage analysis, code chunking, AI calls) but instead of writing the results to files, it should print the generated tests to the console.The output should clearly indicate which file each generated test belongs to.
Describe alternatives you've considered
git(clunky workflow).Additional context
This is from the New Ideas Backlog.