Unit tests are not really meant to test whether the code does what it's supposed to do initially, but more about making sure that it _keeps_ working when you're

Unit tests are not really meant to test whether the code does what it's supposed to do initially, but more about making sure that it _keeps_ working when you're changing a bunch of stuff. For a pre-traction startup/MVP, the latter doesn't really matter. It will be the first version of the product, so there won't be a lot of changes. If the first version of the product gets traction, then it becomes interesting to write more tests.