So, you are selling a product about documents without granting it works now and that it will keep working?
Why not writing on top of your product page “nothing is tested in here”?
You know that would hurt, and also you know “not testing” is a lie you tell to yourself. You are manually testing every new feature your’re shipping, ’cause that’s how you confirm the feature is being shipped, but you probably just don’t know how to automate that test ensuring that, on the next release, that feature will still work.
But that is a whole new different kind of problem, I mean, the not knowing how to automate tests … isn’t it?
On the other hand, believing that users will be so happy and engaged once they’ve lost every document they’ve spent time writing down and just because they upgraded the software looks a bit too naive in 2017.
Having some basic test that ensures a functionality work is the only way to move forward any project that would like to become popular, unless you are a very big company and developers don’t care, believing if it’s from that company it must be robust and tested for sure (you’d be surprised how many famous products out there lacks tests and indeed have horrendous bugs).
As summary, like other said, and without even mentioning TDD which is a different level not too friendly for (test) beginners, having some solid foundation is not a waste of time or a loss of money.
Every time you test manually something and you decide “let’s ship it” is a waste of time if you don’t keep that test that demonstrated yourself the software works. You spent time, without keeping the test around, which in turns it means you’re wasting non sustainable time to test at runtime without being able to recycle that wasted time later on, and on top of that, you are writing posts about how unnecessary is to test personal software.
I hope you’ll agree what you are doing now it’s a bit of a counter-sense that does not need to be widely adopted.
Good luck anyway with your personal projects.
