The work life of an automated tester often seems to be an endless game of catch-up. A sprint starts and developers begin their work, submitting their code somewhere in the middle to the end of the sprint. The tester then has to scramble to write their automation ASAP.

This situation is less than ideal. Deadlines are missed, stories roll into the next sprint or even work – automation is relegated as “nice to have”. So what is one to do? How can test automation keep up with development while maintaining a high standard of quality? The answer is simple:

Test code scaffolding

In this presentation, Hal will describe what test code scaffolding is and how to best implement it. He will walk through a hypothetical example of it in practice using a user story and code examples.

Takeaways from your talk:

  • How to increase the velocity and efficiency of your test automation team
  • How to get test automation involved at the beginning of a sprint, not just the middle and end
  • Practical tips and demonstrations of how to more fully integrate the QA and Development teams

May 10 @ 14:15
14:15 — 15:00 (45′)

Hal Deranek