Testing is about trying to find bugs, and how do you do this? Because you compare what you expect a program to do with what the program does. Where is this information in the requirements? And I'm not saying like a Word document that contains the requirements or UML. It doesn't matter. The requirements can be in your mind. At some point there's this notion of what the program should do. So specification based techniques are the ones that help you look at the requirement and identify interesting test cases. This is not new. Again, this dates from the 80s. We've became very good at coming up with techniques. If you really want to be a little bit more systematic

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode