In order to make sure that our code base keeps working and new features don't break existing behaviour, we need to introduce tests into the code base. Having a good test coverage also allows us to find problems with changed HTML elements quicker.

Advantages of this feature:

• Finding code breaks quicker
• Less time needed to review PRs and fixes
• Integration ready for release GitHub pipeline

Possible ways of achieving this while keeping control:

• Starting to add tests for all the features that are deployed starting from now on
• Slowly covering the most important and most used features with tests

Bountysource this Issue

Feel free to comment with adjustments and improvements