My approach to testing is not to be obsessed with the latest, greatest framework or 100% code coverage. I try to start with just one or two tests to actually h

My approach to testing is not to be obsessed with the latest, greatest framework or 100% code coverage. I try to start with just one or two tests to actually help do things that are tedious or require multiple steps. It takes some time to automate a good test but once you do it immediately starts saving time because you don't have to run the same sequence a thousand times while developing. You can think of it more like a macro that saves you time. Once you write the main test it's easy then to run it with all combinations of good and bad input. By doing that you'll often wind up hitting a pretty good percentage of your code. Then as bugs are discovered due to unexpected input you can just keeping adding more input situations.