The TCR tool only reverts the code files, and keeps the failing test. The original TCR was also reverting the tests. These 2 behaviors lead to quite different workflow. The original TCR encourages:
to add "disabled" tests that get "re-disabled" when they fail
to take even smaller steps, and to use the tidy-first workflow: "Make the change easy, then make the easy change"
Feature Description
This could be an option to TCR (ex: --also-revert-tests). It could also become the default behavior, and make the current behavior available with an option (ex: --nice)
Alternatives
An alternative is to completely drop the current behavior, and stick only to the Real TCR.
Additional Context
I needed this feature on the Baby Steps Golf Kata (https://github.com/philou/kata-babystepsgolf). I ended up reverting to straightforward TCR scripts. I also needed to run the TCR manually (and not systematically on save, as I wanted participants to give a special commit message).
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Contact Details
philippe.bourgau@gmail.com
Feature Request
The TCR tool only reverts the code files, and keeps the failing test. The original TCR was also reverting the tests. These 2 behaviors lead to quite different workflow. The original TCR encourages:
Feature Description
This could be an option to TCR (ex: --also-revert-tests). It could also become the default behavior, and make the current behavior available with an option (ex: --nice)
Alternatives
An alternative is to completely drop the current behavior, and stick only to the Real TCR.
Additional Context
I needed this feature on the Baby Steps Golf Kata (https://github.com/philou/kata-babystepsgolf). I ended up reverting to straightforward TCR scripts. I also needed to run the TCR manually (and not systematically on save, as I wanted participants to give a special commit message).
Code of Conduct