If you spend too much time planning you run the risk of never launching. I can sit here and refine my product forever, but at a certain point you just need to pull the trigger and launch the damned thing.
I don't think edw519 said anything about "refine[ing] my product forever."
But having a thorough test plan better be a part of your project roll-out. No one wants to go through the rabbit holes of corporatized QA team B.S. but product refinement is a different topic entirely than the point of his comment, which was testing that product before launching it to the masses.
If you think your product won't be seen by many customers, well OK. Set it free. If you have a major push behind it, however, and know 100's of thousands of people are going to be mashing it to death in the first few hours or days, adding a time buffer for testing beyond your close family and friends is wise advice. It will save you money in the long run, too.
The alternative is to become buried under an avalanche of crash reports, bad reviews and ratings. And, conversations like, "If only we'd had more time to test this thing."
But there will always be something that might be the next bug, but perhaps not really keeps people from using your product as well. There is a fine line there. And I agree with 'aytekin' below, probably having more features in a product leads to more bugs and thus difficult launches.
Yes, having so many bugs -- they must either be awful at programming, or tried to release too many features with not enough testing. Reducing features probably would have helped a lot.
Unless you are Blizzard, you can't have a SaaS with a catastrophic launch and still have people think of you as a bunch of swell guys and gals at the end of the day.
