In this our final episode, we cover some important topics which are key to successfully adopting Acceptance Testing, and also consider the critical question of when Acceptance Testing is worth the effort & when it's not!
Paul share's his own experiences with the adoption of Acceptance Testing and some things you can do to improve your chances of success including the importance of a SOLID software design and architecture when adopting Acceptance Tests.
We'll check in on a close cousin of Acceptance Testing: BDD, and see where the two approaches overlap, what problems they solve, and what the actual differences are between them to help you make better decisions about which is right for you.
We'll finish it up by considering the kinds of projects where Acceptance Testing is valuable and reflect on some famous examples of software that went wrong. Not because of bugs, but missing requirements!
You'll get a few last tips as to how to assess your own projects to see if they're likely to benefit from adopting Acceptance Testing. If you decide that Acceptance Tests might be right for your team, Paul proposes his own 3 laws of Acceptance Testing to guide your implementation.
And finally, catch up with the team as they put the finishing touches to their HP-35 Calculator and see it all come together (including those pesky UI Tests!!)