Post

Something early career software engineers struggle with is the code quality of the tests. The tests ought to be readable and maintainable like your main code; not an unmaintainable copy pasta mess. Invest in tools to make your tests concise.

12/12/24, 4:40 pm0 reposts10 likes

animetrashpanda.bsky.social

@animetrashpanda.bsky.social

12 Dec 2024

The advent of test code written by AI has made this problem so much worse. Now there is code coverage, but the tests are not understood or test the wrong thing.

Almog

@almog.xyz

12 Dec 2024

Advice I got from an amazing engineer early in my career about tests: 1. Name tests shouldXYZ (e.g. shouldComputeScoreWhen...) - this makes you think about the purpose of the test 2. Structure them with Given/When/Then sections - this makes it clear which parts are setup, tests and assertions

ahmet alp balkan

@ahmet.dev

12 Dec 2024

In my experience, well-maintained critical components usually have a 1:1 lines of code to test code ratio in Go —sometimes tests are more. If they’re the majority of your codebase, they deserve to be crafted better.