Change Details

For the QS Automation Team to intake and work on (no action required by others) for FY26/27. To support Fy26-27 priorities for Developer Experience and help provide faster feedback cycles to developers, define and create 5 Critical User Journey tests using end to end UI automation. Work will need to: Determine the framework to use (Cypress, Playwright, WebdriverIO) Determine where the code should live Determine the scope of tests Determine what should be mocked within the tests Implement the tests

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 (no action required by others) for FY26/27. To support Fy26-27 priorities for Developer Experience / SRE and help provide faster feedback cycles to developers, define and create 5 Critical User Journey tests usanswer the following question: "How do we know things are working end to end UIproperly in a fully automation.ted deployment pipeline?" Work will need to: Determine the framewhat "work to use (Cypress, Playwright, WebdriverIO)ing properly" means Determine where the code should liveat coverage is given by unit + integration tests in terms of User Experience (ie what is validated through existing unit testing) Determine the scope of testswhat additional tests may need to be created Determine what should be mocked within theframework to use, environment to use (Pretrain? Read-only teststing on production?) Implement theDetermine 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.