I think there's a great balance here in these environments:
- write tests as part of figuring out the implementation (basically: automate the random clicking you're doing to test things anyways)
- Make these tests really loose
- Just check them in
Being unprecious about test coverage means you just write a handful of "don't blow up" tests for features, that help you get the ball rolling and establish at least a baseline of functionality, without really getting in the way.
- write tests as part of figuring out the implementation (basically: automate the random clicking you're doing to test things anyways)
- Make these tests really loose
- Just check them in
Being unprecious about test coverage means you just write a handful of "don't blow up" tests for features, that help you get the ball rolling and establish at least a baseline of functionality, without really getting in the way.