new entry for 9th

Lerntagebuch.md

@@ -226,3 +226,19 @@ For the group project we can keep in mind that in order to write proper unit tes
 
 ### repetition
 Unit tests have to be independent. As a result, there shall be not state spanning across multiple tests. The order of execution should never matter for unit tests. Every unit test can basically be seen as its own program. 
+
+## lecture 9th January 2024
+
+### takeaway
+- which tests to automate
+- FIRST RTFM
+- most automated tests are unit tests
+- can be created using test driven development
+- TDD leads to 100% requirements coverage
+- red green refactor
+
+### perception
+For the group project we can try to use test driven development. Paired with committing after pleasing a requirement or completing a refactoring step we can adhere to clean commits. This will ensure a testable architecture and a good git history.
+
+### repetition
+Code coverage is bad as a key performance indicator as there can be pieces of code for which tests are not needed. Enforcing 100% code coverage as a result will lead to irrelevant tests that worsen the maintainability of the project. Test driven development does not lead to 100% code coverage. However it leads to 100% requirements coverage.