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:
⚡️ How much time do you spending coding in a coding job?
⚡️ How long should you spend on a take home coding challenge?
⚡️ Tabs or spaces?
30: What do you get from going to a tech meetup?
29: What's wrong with developer culture?
28: How do you stay motivated?
27: How do you deal with crazy bugs?
26: What is functional programming?
25: Do you need to be good at maths to become a programmer?
24: Should you write about what you've learnt?
23: How do you write a good CV?
22: Why should you write tests?
⚡️ What does it mean to be a full stack developer?
⚡️ How closely should you match a job description before applying?
21: How do you get started with open source?
20: What's it like to attend a tech conference? (Live at Future Sync)
19: What's it like being a remote developer?
18: What's the interview process for a tech job?
17: How do you find a mentor?
16: When should you specialise?
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
Lex Fridman Podcast
The Unbelivable Truth - Series 1 - 26 including specials and pilot