Is your feature request related to a problem?
The current process automatically appends generated tests to files. This is fast, but it gives the user little control over the final output. The user might want to review, edit, or reject a generated test before it's saved.
Describe the solution you'd like
Implement an interactive mode, likely triggered by a flag like --interactive. In this mode, after a test is generated, the tool would:
- Display the generated test to the user in the console.
- Prompt the user with options, such as:
- Approve (a): Save the test to the file.
- Edit (e): Open the generated test in the default text editor (
$EDITOR) for manual changes before saving.
- Reject (r): Discard the test and move to the next one.
- Quit (q): Exit the process.
This gives the user fine-grained control over the test generation process.
Describe alternatives you've considered
- A
--dry-run mode to see all potential changes at once (less granular control).
- Requiring the user to manually review files after the run (less convenient).
Additional context
This is from the New Ideas Backlog.
Is your feature request related to a problem?
The current process automatically appends generated tests to files. This is fast, but it gives the user little control over the final output. The user might want to review, edit, or reject a generated test before it's saved.
Describe the solution you'd like
Implement an interactive mode, likely triggered by a flag like
--interactive. In this mode, after a test is generated, the tool would:$EDITOR) for manual changes before saving.This gives the user fine-grained control over the test generation process.
Describe alternatives you've considered
--dry-runmode to see all potential changes at once (less granular control).Additional context
This is from the New Ideas Backlog.