Many failures in browser testing for Create:Source Code
This issue is seeking clarification on how to handle Quality issues caused by browser automation.
For groupsource code we currently have 75 P2s with the Quality tag
For example:
Questions
- Do these need to be worked on as any other P2 issue by the BE team?
- If the tests failed, why does it not cause a "broken master" issue, does this mean the tests are quarantined?
Edited by Sean Carroll