My previous startup didn't do much in way of testing early on and the end users certainly felt that. Even later on the things I worked on didn't get test covera

My previous startup didn't do much in way of testing early on and the end users certainly felt that. Even later on the things I worked on didn't get test coverage because it wasn't considered a priority. Now I'm at a startup where it's just myself and another engineer working on the product. He was keen on testing, so we chose a testing framework, and now we include tests when we push code. My advice: Pick a testing framework as a team, learn it, use it. Start writing tests for your previous code. This will be painful and you'll probably have to refactor a lot. That's just how it goes, but your product will be better for it. And in the future if code being pushed doesn't have tests, it doesn't get released. That works for us and it worked for me.