> There's a lot I can respond to in this post, but I think the bottom line is: if you have not experienced the problem, count your blessings.
You don't even specify what problem is it. Again, this is a solution searching for a problem, and one you can't even describe.
> Lots of places do face these problems, with test suites that take hours or days to run if not parallelized.
What do you mean "if not parallelized"? Are you running tests sequentially and then complaining about how long they take to run?
I won't even touch on the red flag which is the apparent lack of modularization.
> And while parallelization reduces latency, it does not reduce costs, and test suites taking 10, 20, or 50USD every time you update a pull request are not uncommon either
Please explain exactly how you managed to put together a test suite that costs up to 50€ to run.
I assure you the list of problems and red flags you state along the way will never even feature selective testing as a factor or as a solution.
You don't even specify what problem is it. Again, this is a solution searching for a problem, and one you can't even describe.
> Lots of places do face these problems, with test suites that take hours or days to run if not parallelized.
What do you mean "if not parallelized"? Are you running tests sequentially and then complaining about how long they take to run?
I won't even touch on the red flag which is the apparent lack of modularization.
> And while parallelization reduces latency, it does not reduce costs, and test suites taking 10, 20, or 50USD every time you update a pull request are not uncommon either
Please explain exactly how you managed to put together a test suite that costs up to 50€ to run.
I assure you the list of problems and red flags you state along the way will never even feature selective testing as a factor or as a solution.