Hey guys, I notice lately that there is a lot of talk about product development without paying enough attention to testing as part of that process. The right testing strategy is extremely important to the success of this product in the market. That's why I want to share with you these practices for creating a testing strategy for your business.
https://mobidev.biz/blog/software-testing-strategy-best-practices
I hope you'll find it helpful.
As a full-stack developer with years of experience working in both small and large teams, one key takeaway for me has been: bugs are inevitable. Whether developers rigorously test code, or whether there are dedicated QA engineers on board, or even if you utilize unit, e2e, acceptance, or any other testing methods, issues can still arise. For early-stage startups and small teams, I believe the emphasis shouldn't solely be on achieving 100% test coverage. Instead, it's even more crucial to establish effective ways to address these bugs, communicate transparently with users, and empower them to contribute to and be an integral part of your product's evolution.
As a full-time backend software engineer I could spend days talking about testing practices. But in the context of indie hacking I'd say - don't bother. Automated tests are a waste of time for a small piece of software developed as a side hustle by a one/two-man team.
I've made that mistake before - I could have launch my product like 3 month earlier to the same quality if I just skipped tests altogether.
That means you guys wrote 3 months worth of tests. How is that possible? For a small product launch, I mean? 3 months worth of tests is A HUGE LOT of tests. But tests are mundane and...kinda easy. I'm wondering :)
A year in development, 3 month worth of tests. That's not even to full coverage, only the critical and most complex parts. Proper testing isn't mundane, it takes time.
Proper testing IS mundane, writing testable and correct code isn't mundane and takes time. :)