For the last two JIRA releases we have been working hard to revamp our in-browser acceptance test suite by developing a library of reusable page objects. In this three-part blog series (part one, part two), I talk about what we did and how JIRA plugin developers can make use of that work. In this final part I will show how you can make use of our JUnit4 utilities to abstract away repetitive activities performed in your acceptance tests and thus further reduce code duplication and improve readability.