[codextremist]

I couldn't agree more. Over the last 5 years I've changed the way I think about testing. Why would u bother about testing in the beginning when your product is constantly evolving? Also, a senior and organized team helps a lot in this process. I'm currently working with two senior developers and we feel that testing can still be postponed safely until we grow our team or our product becomes more mature and interfaces gets more solid and well defined. Nowadays these are my golden rules for testing a small size project/product:

1 - e2e tests for flows and interfaces that are less likely to change.

2 - write unit tests for core models that are specially difficult to test e2e or core models with complex business rules (if it's a backend code, usually your db table with the highest number of relations)