Should I write unit tests before the MVP is ready?

Question

Software testing

Should I write unit tests before the MVP (minimum viable product) is ready? What arguments do you have for and against, please share your experience.
— A team with little to no experience writing unit tests and that has switched to scrum.

Answer 1

It's not just about maintaining the code. With tests, if you write them before a feature, IMHO the most productive and fastest development.
Firstly, this is a detailed technical specification. And any TK speeds up the process.
Secondly, you don’t need to spank the browser with every sneeze. Fill out forms by hand, etc. Plus, if there are several access roles or related processes, then manually check the crap.
Thirdly, it supports the code in the future, is indispensable for refactoring and is an excellent documentation. You need to remember the process and what is the logic - you print the test on the printer and remember it for coffee. In short, I recommend.

Answer 2

Write smoke tests for critical places and that's enough. Otherwise, it will turn out like in this article , where a person built an architecture for 4 months with zero design experience and wrote tests for three weeks per module, instead of rolling out an MVP