Autonomous teams supported by microfrontends can develop the features incomparably faster than the ones forced to work with a monolithic codebase. Unfortunately, when working within one large repository, the advantage is quickly lost due to the need to test the entire codebase in order to ensure that the changes haven’t introduced any regressions. Thanks to the introduction of (product) feature driven design patterns supported by the right tooling it is possible to significantly shorten the time required to verify if the changes will pass the quality gates. Turborepo and its caching abilities help with testing precisely the areas affected by the update, while leaving out the features that haven’t changed at all, helping to expedite the release processes.