L'audio de cet épisode peut être endommagé.
How to fix it?
À PROPOS DE CET ÉPISODE
In this episode, I talk with Zach Dennis about his experience with TDD, the benefits of test first vs test after, the pitfalls of being a TDD purist when working with a team, and giving yourself permission to do things in new and novel ways.
Links:
Anglais
États-Unis
RECHERCHER LES ÉPISODES PASSÉS
Rechercher les épisodes précédents de The Ruby Testing Podcast.
AUTRES ÉPISODES DANS CE PODCAST
I'm taking a break from a regular publishing schedule to work on some other things, including writing a Rails testing book.
Links:
Rails Testing for Beginners
Learn Rails Testing in a Month
Josh Clayton and I talk about factories vs. fixtures, mystery guests, obscure tests, and Factory Bot.
Links:
Josh Clayton on Twitter
Factory Bot
Upcase
Ben and I talk about how to decide what to write tests for, how pair programming relates to testing, and Tuple, a tool Ben is working on to help facilitate remote pair programming.
Links:
Tuple's Pair Programming Guide
Tuple
Ben Orenstein on Twitter
Growing Object-Oriented Software, Guided…
Corey and I discuss our approaches to TDD and refactoring.
Links:
Corey Haines on Twitter
Corey's blog
Understanding the Four Rules of Simple Design (with discount code!)
Coderetreat
Refactoring
Test-Driven Development: By Example
Chris Kottom and I talk about some of the differences between RSpec and Minitest as well as how to decide which testing framework to work with.
Links:
Chris's blog
Chris Kottom on Twitter
The Minitest Cookbook
Learn API Development with Rails 5
Avertissement: Le podcast et les illustrations intégrés sur cette page proviennent de Jason Swett, qui est la propriété de son propriétaire et n'est ni affilié ni approuvé par Listen Notes, Inc.
MODIFIER
Merci de nous avoir aidé à tenir la base de données de podcasts à jour.
