Why do I find bugs but still have no quality strategy?

You find bugs. That takes a sharp eye, and it is not nothing. But you call this a strategy, and it isn't one. A strategy says what you are protecting before the attack comes. You only react after it does. Here is the plain fact: you have never written down what "quality" means for this product. Not vague words like "it should work well." A real definition — which failures matter, which don't, and why they don't. Without that, every test you run is just a guess wearing a badge. This is within your power to fix today. You do not need someone to hand you a framework. You need to sit down and decide, in writing, what you are actually building toward. Then your testing will have a target instead of a twitch.