In this episode, I talk with Paul Ganssle about a fun workflow that he calls pseudo-TDD.
Pseudo-TDD is a way to keep your commit history clean and your tests passing with each commit.
This workflow includes using pytest xfail and some semi-advanced version control features.
Some strict forms of TDD include something like this:
write a failing test that demonstrates a lacking feature or defect
write the source code to get the test to pass
refactor if necessary
repeat
In reality, at least for me, the software development process is way more messy than this, and not so smooth and linear.
Pauls workflow allow you to develop non-linearly, but commit cleanly.
Special Guest: Paul Ganssle.
Sponsored By:
PyCharm Professional: Try PyCharm Pro for 4 months and learn how PyCharm will save you time. Promo Code: TESTANDCODE22
Links:
A pseudo-TDD workflow using expected failuresepisode 171: How and why I use pytest’s xfail – Paul Ganssleepisode 165: pytest xfail policy and workflowepisode 162: Flavors of TDD<p>In this episode, I talk with Paul Ganssle about a fun workflow that he calls pseudo-TDD.<br>
Pseudo-TDD is a way to keep your commit history clean and your tests passing with each commit.<br>
This workflow includes using pytest xfail and some semi-advanced version control features.</p>
<p>Some strict forms of TDD include something like this:</p>
<ul>
<li>write a failing test that demonstrates a lacking feature or defect</li>
<li>write the source code to get the test to pass</li>
<li>refactor if necessary</li>
<li>repeat</li>
</ul>
<p>In reality, at least for me, the software development process is way more messy than this, and not so smooth and linear.</p>
<p>Pauls workflow allow you to develop non-linearly, but commit cleanly.</p><p>Special Guest: Paul Ganssle.</p><p>Sponsored By:</p><ul><li><a href=”https://testandcode.com/pycharm” rel=”nofollow”>PyCharm Professional</a>: <a href=”https://testandcode.com/pycharm” rel=”nofollow”>Try PyCharm Pro for 4 months and learn how PyCharm will save you time.</a> Promo Code: TESTANDCODE22</li></ul><p><a href=”https://www.patreon.com/testpodcast” rel=”payment”>Support Test & Code in Python</a></p><p>Links:</p><ul><li><a href=”https://blog.ganssle.io/articles/2021/11/pseudo-tdd-xfail.html” title=”A pseudo-TDD workflow using expected failures” rel=”nofollow”>A pseudo-TDD workflow using expected failures</a></li><li><a href=”https://testandcode.com/171″ title=”episode 171: How and why I use pytest’s xfail – Paul Ganssle” rel=”nofollow”>episode 171: How and why I use pytest’s xfail – Paul Ganssle</a></li><li><a href=”https://testandcode.com/165″ title=”episode 165: pytest xfail policy and workflow” rel=”nofollow”>episode 165: pytest xfail policy and workflow</a></li><li><a href=”https://testandcode.com/162″ title=”episode 162: Flavors of TDD” rel=”nofollow”>episode 162: Flavors of TDD</a></li></ul>