Session Details

Writing testable code (even if you don't test it) Edit

Regular Session

You should unit test everything, right? At least the important, mission-critical parts of your applications. Right? Unfortunately, not every developer is able (for a number of possible reasons) to properly test the code they write. But there's a weird relationship between good code and code that is tested. Sure, tests ensure that the code works, and that's good, but writing code that is able to be tested tends to make the code better by itself. In order to make testing easy, your code will tend to be decoupled and cohesive. You'll likely implement some of the SOLID principles (even if you don't know what they are). Testable code is better code - whether or not you actually test it or not. Testable code doesn't mean bug-free, but it does mean more maintainable code, which will make finding and fixing bugs easier and help reduce the risk of introducing bugs in the future. In this session, we'll look at things you can do to improve your code by making it testable - unit tests optional.
Adam Barney

Barney Consulting, Inc.


A software development conference in the Louisville, KY area on March 28 - 30, 2018 designed to cover all aspects of software development regardless of development stack.

Contact Us
Keep in Touch