Sign up to save your podcasts
Or
Share 68: test && commit || revert (TCR) - Thomas Deniffel
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
68: test && commit || revert (TCR) - Thomas Deniffel
With conventional TDD, you write a failing test, get it to pass, then refactor.
Then run the tests again to make sure your refactoring didn't break anything.
But what if it did break something?
Kent Beck has been recommending to commit your code to revision control after every green test run.
Oddmund Strømme suggested a symmetrical idea to go ahead and revert the code when a test fails.
Kent writes that he hated the idea, but had to try it.
Then wrote about it last September.
And now we have TCR, "(test && commit) || revert".
What's it feel like to actually do this?
Well, Thomas Deniffel has been using it since about a month after that article came out.
In this episode, we'll hear from Thomas about his experience with it.
It's a fascinating idea. Have a listen and let me know what you think.
Special Guest: Thomas Deniffel.
Sponsored By:
- PyCharm Professional: Try PyCharm Pro for an extended 4 month trial before deciding which version you need. If you value your time, you owe it to yourself to try PyCharm. Promo Code: TESTANDCODE22
Links:
- test && commit || revert — Kent Beck's original article
- TCR: (test && commit || revert). How to use? Alternative to TDD? — Thomas Deniffel's article
- TCR Variants (test && commit || revert)
- TCR: A pulverizer for coding tasks — Another interesting opinion from someone else trying TCR - Jason Crawford
- (test && commit || revert) Questions Answered — Written after this interview.
★ Support this podcast on Patreon ★
View all episodes
By Brian Okken
4.7
7070 ratings
With conventional TDD, you write a failing test, get it to pass, then refactor.
Then run the tests again to make sure your refactoring didn't break anything.
But what if it did break something?
Kent Beck has been recommending to commit your code to revision control after every green test run.
Oddmund Strømme suggested a symmetrical idea to go ahead and revert the code when a test fails.
Kent writes that he hated the idea, but had to try it.
Then wrote about it last September.
And now we have TCR, "(test && commit) || revert".
What's it feel like to actually do this?
Well, Thomas Deniffel has been using it since about a month after that article came out.
In this episode, we'll hear from Thomas about his experience with it.
It's a fascinating idea. Have a listen and let me know what you think.
Special Guest: Thomas Deniffel.
Sponsored By:
- PyCharm Professional: Try PyCharm Pro for an extended 4 month trial before deciding which version you need. If you value your time, you owe it to yourself to try PyCharm. Promo Code: TESTANDCODE22
Links:
- test && commit || revert — Kent Beck's original article
- TCR: (test && commit || revert). How to use? Alternative to TDD? — Thomas Deniffel's article
- TCR Variants (test && commit || revert)
- TCR: A pulverizer for coding tasks — Another interesting opinion from someone else trying TCR - Jason Crawford
- (test && commit || revert) Questions Answered — Written after this interview.
★ Support this podcast on Patreon ★
More shows like Test & Code
View all
Software Engineering Radio - the podcast for professional software developers
272 Listeners
The Changelog: Software Development, Open Source
283 Listeners
Thoughtworks Technology Podcast
41 Listeners
Data Skeptic
483 Listeners
Talk Python To Me
592 Listeners
Software Engineering Daily
624 Listeners
Soft Skills Engineering
269 Listeners
Python Bytes
213 Listeners
Data Engineering Podcast
142 Listeners
Syntax - Tasty Web Development Treats
982 Listeners
Practical AI
190 Listeners
The Stack Overflow Podcast
64 Listeners
The Real Python Podcast
140 Listeners
Oxide and Friends
47 Listeners
The Pragmatic Engineer
52 Listeners