142 - 6 Ways to improve your code tests
Download and listen anywhere
Download your favorite episodes and enjoy them, wherever you are! Sign up or log in now to access offline listening.
Description
Change log: - All the https://github.com/howToCodeWell/course-notes for https://www.youtube.com/watch?v=PbiYll21Jxg&list=PLZdsdjcJ44WU_cY2Y1LFLnmsSjFD5BZLZ has been written. This is available on https://github.com/howToCodeWell/course-notes - I’ve started work on transcribing that course. This will take a long time....
show more- All the code notes for Docker for beginners course has been written. This is available on GitHub
- I’ve started work on transcribing that course. This will take a long time.
- I’ve fixed issues on howtocodewell.net regarding signup, forgotten password and other minor fixes
- I’ve added the functionality to lock and unlock courses. This will turn them into private or public courses that require enrolment
- Use CI pipelines
- Run these locally even if your’e not committing any changes
- Include other code auditing tools such as phpstan or phpmd
- There is no way to test a static method that calls another static method
- If a unit of work cannot be easily tested then it usually means the code is not designed well
- Break up your tests into smaller chunks
- Tests can highlight micro and minor refactors
- Refactor your code and then re test
- Try and do this in a TDD fashion
- Clean up state
- Check for bottle necks which could cause timeouts
- Mock external services or dependancies
- Look into potential memory leaks
- Testing is a contractual agreement between the programmer and the code
- Testing is documentation - Gherkin, Acceptance Criteria, Business requirements
- Testing is boundary setting which helps with focus
- Testing is future proofing
Information
| Author | Peter Fisher |
| Organization | Peter Fisher |
| Website | - |
| Tags |
-
|
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
Comments