We're a small team mostly building MVPs following the Lean Startup Methodologygies and lean development.
Up until now, we've been shipping code without unit tests, in order to get our products or features MVPs out rapidly and get validated learning by having real people use them.
However, one of the MVP is starting to grow in popularity and we're shipping more and more either new features or incrementally improving existing ones to better fit customer's needs.
On one hand, we don't want to waste time delivering a perfectly coded/tested feature that turns out to be useless/wrong assumption (we could have figured that out without "wasting" time testing the code) but on the other hand, we're also conscious that shipping something quickly/untested might create bugs that keep us from getting our learnings by degrading the experience.
I feel like our MVP is actually turning into a real product, which might be the origin of the issue here but I was wondering if you had any advice on how we can keep experimenting quickly without compromising the quality of the production environment. Is a TDD approach compatible with quick experimentation? (Especially since we're not used to using this approach)