Why should you unit test? What should you unit test? And how much?
Today's blog post answers these questions and provides some helpful guidelines.
The post is actually a lightly edited extract of a book on unit testing that I started about 10 years ago but never finished. Still, it has aged reasonably well.
I have a ton of command line utilities and web services that interact with LLM apis, SQL databases, event queues (redis, SQS, etc...), elasticsearch and then some.
I want to test my code at an integration level, for example making sure that my HTTP frontend to the SQL database returns proper excel files when hitting the download endpoint, this kind of stuff.
Looking for a remote role based in the US. I'm a quality-focused engineering lead, best at Python. I build teams, and solve hard problems.
Been a people manager and IC for 9 years, created a global testing practice of 50+ people. Worked in consulting, so I'm fluent with talking to clients and sales.
Graduating a data science master's in October, GPA is 4.0 with 9 classes done, would love a data science role.