DEV Community

loading...

Discussion on: Automated tests before reaching market - worth it or not?

Collapse
kaydacode profile image
Kim Arnett 

I've had experience in both and I vote for tests.

Test the big things, test the things you know aren't going to change next week. It's kind of tedious at first, but where the tests make up for it is once your product is done, and a new version of x dependency is out, you'll know quickly whether something major broke or not. Also a fan of CI like someone else mentioned, and having that test for you.