Code Driven Testing

Image by <a href=”https://pixabay.com/users/kalhh-86169/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=1104066">kalhh</a> from <a href=”https://pixabay.com/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=1104066">Pixabay</a>

Introduction

Okay, I admit the title is a bit of a poke at the hype surrounding “Test driving coding,” but at the same time, this is a serious article about a serious technique that I use but hadn’t given a name until recently. I have done this literally since the first program I wrote, and I will bet many of you also have. I write a block of code, then I call it. With interpreted languages, it was easy, just hit run…

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Tom Chizek

Tom Chizek

Software Engineer by day, Novelist by night