GeePawHill on Nostr: Pro-Tip: Test your validation code, every single failure case. You are likely to find ...
Pro-Tip: Test your validation code, every single failure case.
You are likely to find this tedious and annoying.
If so, it means your design ain't there yet.
If something is important, and your design doesn't make it easy for you to test, before you reach for your auto-mocker, ask yourself if there's a design change that would a) make it easy and b) not mock anything.
Once again, the steering premise: tests and testability are first-class participants in design.
You are likely to find this tedious and annoying.
If so, it means your design ain't there yet.
If something is important, and your design doesn't make it easy for you to test, before you reach for your auto-mocker, ask yourself if there's a design change that would a) make it easy and b) not mock anything.
Once again, the steering premise: tests and testability are first-class participants in design.