Improvement suggestions for engaging with counterpart teams before end to end test breaking changes are merged
Raising this issue ticket to prompt a discussion based on a discussion I raised in the Quality Engineering weekly pt2.
I wanted to hear others strategies or improvement suggestions for interacting with counterpart teams such that changes that need E2E test updates are addressed before they reach master/deployment.
Context - I found myself firefighting the Secure end to end tests due to dashboard changes, and wanted to improve this such that on call engineers aren't always having to take time to investigate and raise failure tickets for my stage.
During the discussion it was suggested that on a feature::addition
label the SET could be @ mentioned, or package-and-qa
could be ran. It was further suggested that this change could be made to the Danger bot.
This issue ticket allows for further asynchronous discussion of process improvements.