We're joined this week by testing expert (and long-time friend of the show) Brian Okken. Brian literally wrote the book on testing with Python (Python Testing with pytest) and has a lot of strong opinions about the value of testing and testing methodologies in general. Thankfully he's as friendly as he is smart, and was happy to lead us through the sometimes-murky waters of software testing.
How did Brian first get into testing, and what advice does he have for those of us just getting started with learning to test our code effectively? What makes a good test (and what makes a bad test)? And what simple questions can you ask to immediately improve your testing game? Find out all this and more in this week's well-tested instalment of A Question of Code.
Mentioned in this episode:
89: Top Tips review: pragmatic learning
88: Top Tips review: document what you learn
87: Top Tips review: enjoy what you do
86: Top Tips review: just get things done!
85: Top Tips review: why should you build your own website?
84: Why should you own a rubber duck?
83: How do you get started with a new framework?
82: What is semantic markup?
81: What is an API?
80: What’s it like behind the scenes of a podcast?
79: How important are CS fundamentals? (with Vaidehi Joshi)
78: How can developers get better at design?
77: Should you use boilerplates?
76: CSS Revisited (Rapid Fire)
75: Why do you need a website of your own? (with Chris Coyier)
73: Why is Python a good starting point for learning to code? (with Michael Kennedy)
72: CSS Extravaganza!
71: How should developers market themselves? (with Shawn Wang)
70: Is "become a developer" still good advice?
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
Acquired