Please show me a solved automated test for the issue in the post.
Even my craptastic company gives me a bunch of devices to test on. And I very deliberately specify very low-end versions of the machines so that I can test against worst-case-scenarios. It's a bonus that sub-optimal hardware is cheap as chips.
My favorite testing device is a $20 burner phone I picked up in the supermarket checkout aisle. If the web site works on that piece of poo, it'll work on anything.
Right now I'm waiting for UPS to deliver an old iPad from Alaska that the IT department bought for me off of fleaBay, just so that I can test on sub-optimal actual hardware.
Testing platforms like SauceLabs, Browserstack etc run on real hardware, even for mobile.
Testing with your own devices is of course better, but a lot more work. Which one you choose doesn't really matter, the point is just that you don't _need_ to have all those resources to do basic compatibility testing, so no excuses.
Ths context is that testing is a solved problem. You are taking specific factual examples I wrote and attempting to debunk them with a general statement that is in agreement with what I wrote. Testing scrollbards can absolutely be tested inside a VM. Pretending that native hardware is needed to cover 99% of the use-cases for scrollbars is kind of silly.
> Even my craptastic company gives me a bunch of devices to test on. And I very deliberately specify very low-end versions of the machines so that I can test against worst-case-scenarios. It's a bonus that sub-optimal hardware is cheap as chips.
You've made my point. This is a solved problem.
