Exploring Five Things Orgs Often Miss When Working with Test Automation Frameworks

Nearly every software development organization grapples with issues working with test automation frameworks that challenge the viability of the frameworks themselves as software tooling automating the gathering of data and feedback reflective of current functional state. Not only does the tool not work for problems the org intended it for; it also presents its own issues that now require

I've actually been called in by couple different organizations to diagnose and suggest fixes for issues that fit this description after they become entrenched, as well as to build replacement tooling. Interestingly, a lot of these issues seem to take on common forms, they seem to result from common trade-offs made developing and maintaining tooling for automated testing, and it seems like they might also align with a common vision for what the organizations are trying to accomplish with testing.

More often than not, it seems like these organizations have simply missed opportunities to avoid these issues proactively. If anybody involved in the development and maintenance of testing tooling understood what it seems like organizations are missing, it seems like they might also know what to look for, so as to avoid the issues that seem to result from them proactively.

This presentation will navigate What it seems like they are missing, as well as the Who, Where, How, and Why that often seem involved.

• Intermediate
• Development
• Other