DiscoverTest & Code - Software Testing, Development, Python
Test & Code - Software Testing, Development, Python
Claim Ownership

Test & Code - Software Testing, Development, Python

Author: Brian Okken

Subscribed: 1,978Played: 7,581


Test & Code is a weekly podcast hosted by Brian Okken.
The show covers a wide array of topics including software development, testing, Python programming, and many related topics.
When we get into the implementation specifics, that's usually Python, such as Python packaging, tox, pytest, and unittest. However, well over half of the topics are language agnostic, such as data science, DevOps, TDD, public speaking, mentoring, feature testing, NoSQL databases, end to end testing, automation, continuous integration, development methods, Selenium, the testing pyramid, and DevOps.
74 Episodes
In this episode, I talk with Derrick Mar, CTO and co-founder of Pathrise.This is the episode you need to listen to to get ready for software interviews.We discuss four aspects of technical interviews that interviewers are looking for:communicationproblem solvingcodingverificationHow to practice for the interview.Techniques for synchronizing with interviewer and asking for hints.Even how to ask the recruiter or hiring manager how to prepare for the interview.If you or anyone you know has a software interview coming up, this episode will help you both feel more comfortable about the interview before you show up, and give you concrete tips on how to do better during the interview. Special Guest: Derrick Mar.
This is a "Yay! It's PyCon 2019" episode.PyCon is very important to me.But it's kinda hard to put a finger on why. So I figured I'd ask more people to help explain why it's important.I ask a few simple questions to people about Python and PyCon and get some great insights into both the language popularity and the special place this conference holds to many people.
Some typical technical interview practices can be harmful and get in the way of hiring great people. April Wensel offers advice to help fix the technical interview process.She recommends:* hire for mindset and attitude* look for empathy and mentorship skills* allow candidates to show their strengths instead of hunting for weaknesses* have the candidate leave feeling good about themselves and your company, regardless of the hiring decisionSome topics discussed:* interview questions to bring out stories of skills and successes* stereotype threat* diversity* interview hazing* white boards* coding challenges* unconscious bias* emotional intelligence* myth of talent shortage* pair programming and collaboration during interviews* mirrortocracy* cultural add vs cultural fit* empathy* mentoringThis episode is important for anyone going into a technical interview, as a candidate, as a hiring manager, or as a member of an interview team. Special Guest: April Wensel.
Nina Zakharenko gives some great advice about giving tech talks.We talk about a blog series that Nina wrote called "The Ultimate Guide To Memorable Tech Talks". This episode is full of great help and encouragement for your own public speaking adventures.Some of what we discuss:* overcoming the fear of public speaking* breathing and pausing during talks* planning your talk as well as planning your time to get ready for the talk* writing proposals and getting feedback on proposals* Nina's talk in PyCascades on programming Adafruit chips* types of talks that are often rejected* pre-recording demos to avoid live demo problems* why you should speak, even if you are an introvert* benefits of public speaking* a super cool announcement at the end Special Guest: Nina Zakharenko.
Dane and Brian discuss skills needed for people that become software developers from non-traditional paths.Dane is also writing a book to address many of these skill gaps, Code Like a Pro (, that's currently in an early access phase. Use code podtest&code19 to get a discount. And, sign up as a Friend of the Show ( to enter for a chance to win a free copy of the eBook version.We also discuss the writing process, testing with a multi-language stack, music, art, photography, and more. Special Guest: Dane Hillard.
Andy Hunt and Dave Thomas wrote the seminal software development book, The Pragmatic Programmer. Together they founded The Pragmatic Programmers and are well known as founders of the agile movement and authors of the Agile Manifesto. They founded the Pragmatic Bookshelf publishing business in 2003. The Pragmatic Bookshelf published it's most important book, in my opinion, in 2017 with the first pytest book ( available from any publisher.Topics:* The Pragmatic Programmer (, the book* The Manifesto for Agile Software Development (* Agile methodologies and lightweight methods* Some issues with "Agile" as it is now.* The GROWS Method ( * Pragmatic Bookshelf (, the publishing company* How Pragmatic Bookshelf is different, and what it's like to be an author ( with them.* Reading and writing sci-fi novels, including Conglommora (, Andy's novels.* Playing music ( Special Guest: Andy Hunt.
With conventional TDD, you write a failing test, get it to pass, then refactor.Then run the tests again to make sure your refactoring didn't break anything.But what if it did break something? Kent Beck has been recommending to commit your code to revision control after every green test run.Oddmund Strømme suggested a symmetrical idea to go ahead and revert the code when a test fails.Kent writes that he hated the idea, but had to try it.Then wrote about it last September.And now we have TCR, "(test && commit) || revert".What's it feel like to actually do this?Well, Thomas Deniffel has been using it since about a month after that article came out.In this episode, we'll hear from Thomas about his experience with it.It's a fascinating idea. Have a listen and let me know what you think. Special Guest: Thomas Deniffel.
In today's episode we talk with Kelly Paredes & Sean Tibor. They teach Python in a middle school in Florida, and talk about this experience on the podcast "Teaching Python".I love that they include physical computing right from the start, and everything else they are doing.It's a fun interview. Special Guests: Kelly Paredes and Sean Tibor.
I was recently interviewed on a podcast called "IT Career Energizer Podcast".Phil Burgess is the host of the podcast, and it was a lot of fun.I think it turned out well, and I wanted to share it with you here, with Phil's permission, of course. Special Guest: Phil Burgess.
65: one assert per test

65: one assert per test


Is it ok to have more than one assert statement in a test? I've seen articles that say no, you should never have more than one assert.I've also seen some test code made almost unreadable due to trying to avoid more than one assert per test.Where did this recommendation even come from? What are the reasons? What are the downsides to both perspectives?That's what we're going to talk about today.
Download from Google Play
Download from App Store