Development Decisions

General Development Strategy

1. Creation of ticket in Jira
2. The first person to start development on the ticket moves it to the "Writing Tests"-Column nad creates a branch
3. In the branch the developer writes all the tests needed to verify the feature functionality
4. After finishing the tests, the ticket gets moved to the "Writing Code"-Column
5. Preferably another developer assigns the ticket to themselves and implements the feature to satisfy all tests
6. They then create a Pull Request on Github and add the developer who wrote the tests for the feature as a reviewer
7. The reviewer comments on the code and requests changes, which get discussed and/or implemented by the developer until both developers are happy with the feature
8. The Feature-Branch gets merged into the main-Branch
9. The ticket gets moved to the "Done"-Column in Jira
10. The Development-Process of this feature is finished

Conventional Commits

The Commit-Messages follow the conventional commit standard: https://www.conventionalcommits.org/en/v1.0.0/

Testing

Jacoco has been added to the project to automatically generate Test Coverage reports. In Pull Requests Reviews it should be checked that no important branches have been missed when writing tests.