Spoiler: Nothing is really untestable. Testability is always there, and can be improved.

But why do we say that code is “untestable”? And what makes it so?

What is testability anyway?

In this session, I explore testability of code and systems. What we perceive as testable or untestable – and how that perception impacts the quality of the product. We look at examples from code, to APIs to system level, and see how they impact it. And finally, what we can do to improve it.

I also discuss the 4 attributes of testability: Operability, visibility, controllability and reproducability. Lots of illities.

If you’re interested in this (you’ve come to the right place!), and want some testability goodness for your team, contact me!

Categories: Uncategorized


Leave a Reply

Avatar placeholder

Your email address will not be published. Required fields are marked *