Quality assurance and control are an elementary part of our development process. In order to limit manual effort to the important tasks and to constantly guarantee the highest quality, these are implemented from the beginning as part of a so-called Continuous Integration and Continuous Delivery (CI/CD) pipeline: a sequence of measures and analyses checks each project from the first line of code as well as every further change automatically. Changes are developed in isolation, analyzed, and only applied to the project if the check is successful. In concrete terms, this sequence looks as follows: The code base must compile without errors. Static code analysis: review of changes for potential error sources, consistent code style, and best practices. Automated unit and UI testing: must all be error-free with 60-80% code coverage (depending on your requirements per project; some portions of code cannot be tested automatically). Manual four-eye review of changes by another developer – changes are annotated with any comments, accepted or rejected. Automated deployment of the new app version for internal use. Execution of manual integration tests using a growing test script to check all business requirements. Different milestones have different levels of requirements. This can ensure that a beta version already meets all manual integration tests, while an internal version does not yet need to go through the manual testing process, for example, to efficiently run experiments. However, there will be no public version that has not been put through its paces and subjected to stress tests. Should an unexpected problem occur despite the above measures, each project is equipped with appropriate monitoring and reporting. This allows us to react quickly to any errors that occur and to solve them.