Top Testing Mistakes Startups Make
2 min readMay 21, 2015
This is a quick list of mistakes we constantly see:
- Making assumptions. (ex. it worked yesterday, last month etc)
- Missing the big picture. (does the whole team understand the whole app or site — is everyone testing?)
- Ignoring a small bug or design flaw. (symptom of a larger issue not found yet?)
- Not having a “bug-aware” culture. (does your team care? do you?)
- Not counting bugs monthly or daily. (do you have bug insights or metrics? and/or how to improve them moving forward?)
- Ignoring customer service metrics. (they are usually related to failed testing processes)
- Not calculating the bug-finder ratio. (Who finds most of your bugs? Customers, Testers, Management, Founder etc ?)
- Not accounting for your customers location. (What is the page response like in Australia?)
- Using an emulator to test. (Doesn’t catch modals or javascript properly or print screens and svg graphics)
- Only testing the front-end design?
- Only testing the back-end functionality?
- Can you see your watch your top customers actually use the product? Tools such as hotjar.com make this possible.
- Not having time (obvious)
- Not have resources (obvious)
Jason Hamilton-Mascioli is the Founder of Testlauncher, a web and mobile testing company offering on demand expert testers and full-service managed test services. Follow me @jason_hamiltonm or visit testlauncher.com for more info.