I mentioned them just under different names which you can see on that post. I also explained why most bugs do not penetrate multiple layers of test that are dictated by principles. An "inaccurate result," or "unintended behaviour" have pretty much no way of passing proper verification. The only kind of "bugs" you should be discovering in beta are user requirements that differ from the product. That is why the system is mostly bug-free. Beta is not a testing (verification) environment, it is an approval (validation) environment. As fun as it is to watch you struggle against me with literally no technical knowledge (automatons... hahaha) people really had enough. So did I. Go bother some doctor somewhere about Covid; but please, leave me aloneI didn't even mention software validation or software verification, so good job on putting words in my mouth in an attempt to derail the conversation. All I've asked of you is to prove your idea that a software product "should be more or less bug-free when it reaches Beta stage." Your mention of software validation and software verification are pretty much irrelevant because bugs are not limited to programming or technical errors that can be detected by automatons. An inaccurate result, unintended behavior, or a technically correct behavior that is wrong according to the business process, fall within the definition of a bug.
Many of such bugs can only be found after the product is used by more users, and in their environment, which is what beta testing is.