We have our huge managed package (1st generation, i.e. classic one) and every time when we upload new beta version (even with just a few fixes) it takes up to 3 hours for the whole process to complete - tests execution takes the most part of it.
So I'm wondering if there is a way to bypass/suppress tests execution when uploading beta package. We'd like to have our beta version ready ASAP to install it in QA org, run smoke and start manual testing. And after that we might run apex tests post factum on packaging org to catch additional problems with logic.
When it comes to ordinary code deployment (change sets, ant whatever) SF does not enforce tests execution re sanboxes. And even for production deployment there are some additional options like quick deploy or running just subset of tests to cover only classes with changes in current deployment bundle.
Is there something similar when it comes to managed package upload? What other options do we have to speed up upload process and tests execution? Do we really need to have > 75% of coverage for beta packages or only for final majors?
Any help would be appreciated.