
Sign up to save your podcasts
Or
In this week's installment of Programming By Stealth, Bart takes us down memory lane to 102 episodes ago when he first introduced us to the concept of test-driven development. He explains why back then he taught us how to use QUnit for our TDD work, and why it's no longer in favor with him. It's not just the advancements in technology like ES6, but it's also because QUnit makes it terribly hard to write tests and to interpret what you've written when you've been away from it for a while. He walks us through his criteria for picking a new TDD tool, and why he chose Jest for the job.
He then walks us through a worked example of how to write some simple tests on a module and of course, explains how Jest does its job running our tests. I liked it, even though my head hurt during a bit of it!
You can find Bart's fabulous tutorial shownotes at pbs.bartificer.net.
4.8
99 ratings
In this week's installment of Programming By Stealth, Bart takes us down memory lane to 102 episodes ago when he first introduced us to the concept of test-driven development. He explains why back then he taught us how to use QUnit for our TDD work, and why it's no longer in favor with him. It's not just the advancements in technology like ES6, but it's also because QUnit makes it terribly hard to write tests and to interpret what you've written when you've been away from it for a while. He walks us through his criteria for picking a new TDD tool, and why he chose Jest for the job.
He then walks us through a worked example of how to write some simple tests on a module and of course, explains how Jest does its job running our tests. I liked it, even though my head hurt during a bit of it!
You can find Bart's fabulous tutorial shownotes at pbs.bartificer.net.
829 Listeners
158 Listeners
893 Listeners
2,013 Listeners
543 Listeners
1,287 Listeners
3,125 Listeners
2,092 Listeners
251 Listeners
18 Listeners
568 Listeners
1,199 Listeners
107 Listeners
20 Listeners
71 Listeners
508 Listeners
14 Listeners