Run QA tests via a throttled network
Flaky tests can take a lot of time to fix, especially when they're difficult to reproduce. A substantial proportion of flaky tests fail because the test attempts to perform an action before the previous action is complete and the UI is ready for the next action.
Run new or updated tests via a throttled network to simulate the conditions that can cause some flaky tests to fail. This will give us confidence that the test is written in a way that can cope with expected slow conditions.
We could do this via chromedriver's network_conditions setting. We could have a new scenario that is essentially
Test::Instance::All, but with the
network_conditions configured to slow.
Because that would run all the tests more slowly, it would be great if we could restrict the tests run to only those added/changed in an MR.