Functional tests are taking 25 minutes plus to run across browserStack right now which is killing productivity and hindering changes. Most of the time failures are down to timeouts / hosting errors and / or differences in browser drivers.
Our unit tests are pretty comprehensive and widget-core is fully tested already so this should be pretty low risk.
We should restrict test environment to Chrome only. We can look into running scheduled smoke tests against a wider browser stack at a later date.
Enhancement
Functional tests are taking 25 minutes plus to run across browserStack right now which is killing productivity and hindering changes. Most of the time failures are down to timeouts / hosting errors and / or differences in browser drivers. Our unit tests are pretty comprehensive and widget-core is fully tested already so this should be pretty low risk. We should restrict test environment to Chrome only. We can look into running scheduled smoke tests against a wider browser stack at a later date.