Test Automation is a Social Activity

Test automation is done in solidarity by experts of their craft, right? Without the need for input and discussion with others, right?
We test automators instrument the system under test as we see fit and we rule with an iron fist when it comes to testability, right?

Wrong, wrong, wrong!

Just as testing is a social activity, so is test automation. Sure there are a handful of super stars that perhaps can do it themselves, but those are few and far between (not to mention pricey).
Also, even if you could do it all yourself, you still need to discuss and confer with colleagues. Testers need to be consulted to make sure we cover the risk, that we automate what is worthwhile automating, and don’t get me started on consulting with the developers about instrumenting “their” code to make it more testable. Lo and behold, there are even times when we don’t know the best way to mock the login and integration with Github, and we therefore need to, dare I say it, collaborate with our architect.

How about if we even build a test framework that is going to be used by others? Are there other stakeholders we now need to talk with? Users, to not only be educated, but also to be convinced in using the test framework. Join me in this session where I’ll talk about previous experiences I’ve had, and how test automation is a social activity.