Despite ongoing efforts to “shift left” testing, UI test automation has remained a pipe dream for most teams. To achieve in-sprint UI test automation, tests need to be implemented in that tiny sliver of time between when developers complete the final UI code (with a successful build) and when the sprint is supposed to be completed. Guess what? That rarely happens. Within the sprint, teams can certainly tackle human UI testing (a.k.a. exploratory testing.) But automated UI testing? That’s often delayed until a later sprint…and/or scrapped altogether.