Foundations of a Frontend Platform - Pipelines and Test Infrastructure

Pipelines are usually the starting point for many Frontend Platform initiatives. Setting up how Frontend code needs to be built, split and bundled, what is to be rendered where, when and how are non-trivial choices. Besides that, Pipelines are your gateways to production code, and this is the point where quality-, compliance- and security gates need to be implemented. By centralizing how Frontend Pipelines are defined, you don't only take away a lot of cognitive load from your Frontend Developers, you also gain control over how you bring your code to production. 

Closely related to how you build your code in the pipeline, obviously is how to get it tested. Providing your Frontend developers with a standardized way to perform End-to-End testing, either against mocked backends or against a staging environment, is a huge time saver. Not only do you want to be able to automate spinning up a test environment to run your end-to-end tests in CI against, your Developers' local Development Experience also greatly benefits from the ability to quickly run some automated or manual checks in a standardized way across your organization.