Repo containing links to organisational documents
- Self-explaining naming convention
- Minimal use of comments
- Methods perform one task and one task only
- Error handling (specific and no null checks)
- Team formatting rules are met
- Unit tests written with Test Driven Development (TDD)
- One unit test for one feature
- Classes: constants before variables (public before private) before methods
- Law of Demeter (LoD) practiced
- No duplicate code
- Boy scout rule folowed
- Code deployed to build server
- Peer review
- Tests on buildserver are succesful
- Test cover percentage of at least 80%
Law Demeter (LoD)
- Each unit should have only limited knowledge about other units: only units "closely" related to the current unit
- Each unit should only talk to its friends; don't talk to strangers
- Only talk to your immediate friends
Boy scout rule Leave your code better than you found it
Test Driven Development (TDD)
- You may not write production code until you have written a failing unit test.
- You may not write more of a unit test than is sufficient to fail (not-compiling is failing).
- You may not write more production code than is sufficient to pass the currently failing test.