Michael Larsen, Socialtext
Have you ever felt like you were working at cross purposes with an application you were developing and testing? Have you wished that there were easier ways to interact with your application? Do you struggle with the fact that efforts to automate your application under development yield less than satisfactory results? Perhaps you discover that for every answer or solution what results is more and more questions. I decided to undergo a process of a better understanding of what made the applications I work with testable in the first place. Through that process, I’ve learned a few things that may be helpful to anyone looking to make their product more responsive to both human and external program interactions.
Key takeaways include:
- How Testability and Automatability are separate goals that stand apart but can work together
- What are the “touch points” of my system
- How can I use those in a better way
- What tools do I have at my disposal that will help me examine my products testability
- How can I have conversations with my development team about making our product more testable