Re:Ask HN: How bad should the code be in a startup?
by quickthrower2 on Monday June 08, 2020 @03:48AM
(#23454497)
Unit tests are a lot easier to write though and run faster. I think the trick is to assess risk and don’t try to get 100% coverage for the sake of it
[ Parent
| on HN ]
Re:Ask HN: How bad should the code be in a startup?
by Doxin on Monday June 08, 2020 @04:15AM
(#23454627)
I think that depends heavily on what sort of tooling you're using. E.g. writing unit tests for django is near impossible while integration tests are much easier. The ORM invariably has its tendrils throughout the entire codebase, and mocking it out is a project unto its own.
Re:Ask HN: How bad should the code be in a startup?
by quickthrower2 on Monday June 08, 2020 @06:34AM
(#23455355)
ORMs are excepted in my book. Good point. But DB integration tests are possible; slower than unit but still faster than end to end. I created some recently for a side project to make assertions about full text search behaviour, so I could swap out psql for elastc search (for my sins) and have coverage still.