If you aren't writing tests for your code it means you are writing code which is trivial enough to not need tests, which means you are not working on hard enough problems Only excuse is frontend UI stuff or like gamedev which is a pain to test
@zack_overflow Was about to rage until I saw the last sentence. Accurate.
@zack_overflow If there's ever a situation I can't write a test I'll build my own testing framework - TDD maxi
@zack_overflow Corollary : if you are a good enough programmer, all code is trivial, and you don't need tests! 😂🤣😜
@zack_overflow UI frameworks should still be tested, it's just they're not designed well enough for it.
@zack_overflow "you are not working on hard enough problems" People will read this, but being unable to switch problems (because the easy problems still need to be solved) they will pick difficult *solutions*.
@zack_overflow so. much. this. for UI, separation of concerns, write unit tests for presentation logic, trust the view layer until can't LLMs great to generating unit tests
The game part is not really true.. perhaps some studios avoid functional automation as it is costly and brittle but is still very utilized and most AAAs built their own in-house tooling to help as the industry is moving to the shift-left mindset, can't really do a modern multiplayer without it. Unit testing is comprehensive for engines and crucial gameplay systems have decent unit test bases. Integration testing is also there. On top of that all kinds of performance testing and telemetry is done routinely and often with bots... There are plenty of tests in games.
@zack_overflow Even front end has Playwright you can get extremely detailed tests written out with that.
@zack_overflow i was gonna get angry, but then i realized i have a test per feature, per error for my language it's really the fact that writing software that engages with a large input space requires some type of validation to be productive. i.e. large input space = hard problem
@zack_overflow You can do sanity automated runs for the latter as well; but yeah... very painful to setup from scratch.
@zack_overflow Any good resource to learn how to write good tests? I wanna share with my colleagues - you seem to know what you’re talking about so…
@zack_overflow Your game backend can still have tests.
> you are not working on hard enough problems Niall Ferguson recently argued that people in technology often forget about the past and say that now everything is different even though usually it isn’t (youtu.be/giZC4pCqB4o). Most of the time, new things are just old things with slight variations.
@zack_overflow I have one test file “ping my-shiny-app.com” If no packets drops, we’re good
@zack_overflow > gamedev is a pain to test How do we fix this? You see Class TerminalBytePacket? In a game engine for games played inside a Terminal via Ssh It’s only got automated tests at “def _try_bytes_lists_” Where’s the inspiration for more automated tests? github.com/pelavarre/byov…
@zack_overflow Or it means they were the alpha coder who cashed out and you’re the beta employee paid a salary to write test coverage for the code that made someone else $50m+
@zack_overflow Manual testing though. Underrated these days.
@zack_overflow I read @tursodatabase gushing about simulation testing and felt jealous cause I have no clue when or if ever such technology would come to frontend
@zack_overflow And I would say also research code many times doesn’t need tests.
