We have constantly been updating our Fastfile throughout this chapter as we learned new concepts. Now is our opportunity to actually put some structure and method to our Fastfile—as it is the backbone of our continuous delivery workflow—by adding some best practices. Evaluating and tweaking your Fastfile should be part of your routine, looking for ways to optimally manage and streamline it, so let's go ahead and do that.
The first and last lanes in your Fastfile should be before_all and after_all, system lanes that are called before any other lane and after any other lane, respectively. That is, if you call a beta testing or building lane, rather than duplicate an action in each of those lanes, you can place it in the before_all lane to start before any other lane, or the after_all lane for any cleaning up or exiting actions you would need to call.
Based on the types of lanes you have already established for your Fastfile, a few suggested...