Change Details

For the QS Automation Team to intake and work on for FY26/27. To support Fy26-27 priorities for Developer Experience / SRE and help provide faster feedback cycles to developers, answer the following question: "How do we know things are working properly in a fully automated deployment pipeline?" Work will need to: Determine what "working properly" means Determine what coverage is given by unit + integration tests in terms of User Experience (ie what is validated through existing unit testing) Determine what additional tests may need to be created Determine framework to use, environment to use (Pretrain? Read-only testing on production?) Determine scope of tests Write tests Likely a large effort that will require input from Quality Leads (to determine what functionality is important to exercise for users), Core Experiences, and others.

For the QS Automation Team to intake and work on for FY26/27. To support Fy26-27 priorities for Developer Experience / SRE and help provide faster feedback cycles to developers, answer the following question: "How do we know things are working properly in a fully automated deployment pipeline?" Work will need to: * Define what "Critical User Journeys" are alongside a test automation engineer * Automate Critical User Journeys at an appropriate level (cURL to wikipedia.org? E2E UI automated test?) Likely a large effort that will require input from Quality Leads (to determine what functionality is important to exercise for users), Core Experiences, and others.

For the QS Automation Team to intake and work on for FY26/27. To support Fy26-27 priorities for Developer Experience / SRE and help provide faster feedback cycles to developers, answer the following question: "How do we know things are working properly in a fully automated deployment pipeline?" Work will need to: Determ* Define what "working properly" meansCritical User Journeys" are alongside a test automation engineer Determine what coverage is given by unit + integration tests in terms of User Experience (ie what is validated through existing unit testing) Determine what additional tests may need to be created Determine framework to use, environment to use (Pretrain* Automate Critical User Journeys at an appropriate level (cURL to wikipedia.org? Read-only testing on productionE2E UI automated test?) Determine scope of tests Write tests Likely a large effort that will require input from Quality Leads (to determine what functionality is important to exercise for users), Core Experiences, and others.