# SEE 01.06.2022 Notes

Testing:
- Unit testing:
- Goals:
- #1 FAST FEEDBACK!
- understand the code better + external contributors
- code becomes extensible / testable
- coverage is visible in reporting
- contracts become clearer
- less deployment risk
- How we test
- Mocks
- Typing
- Utilities
- Frameworks
- Where & how testing makes sense
- Testing React data-driven components
- Testing algorithms / back-end services
- Agreements
- Cover new / refactored backend services - at least the main case(s)
- Debug configuration commited for VS Code only
- We mock methods as we go with jest.fn()
- Private + public annotation - do not forget it
- We copy / paste the utility functions from repo to repo (for now). They are small + won't change frequently
- When we refactor a service, we write the test(s) first
- @ Fix 'resolution' tests - goal is to remove mysql dependency in travis

###### tags: `SEE`