Enable Fulfillment Engineers to Write End-to-End Tests
Problem
From Enable engineers to write end-to-end tests:
Currently, SETs are mainly responsible for developing and maintaining test specs at the end-to-end level. We are seeing few contributions from counterpart engineers at this level. In both Career Frameworks (SET Technical Competencies and the Development Department Competencies) at the intermediate level, there is an expectation that quality should be baked in the task and writing tests to improve coverage and uplift quality is a necessary part.
With the recent Test Platform team restructure, we want to begin moving toward our vision of providing the "platform" and guidance that enables teams to develop and own their own E2E tests. In order to do so, we need to better define the current pain points that are preventing teams from contributing, outline solutions and come up with a strategy for transition.
The main goal of this issue is to:
- Build on the existing concepts already outlined in Enable engineers to write end-to-end tests to include current impediments related to Fulfillment and CustomersDot E2E tests specifically
- Come up with a proposal for how we can start the transition process for Fulfillment and best provide coaching and guidance
🌳 Environment
Problem | Solutions | DRI |
---|---|---|
General difficulties running E2E tests locally | Improve Setup and Running CustomersDot E2E Tests Locally | |
Tests lack flexibility for diverse local environment configurations (ex: issues with different locales, cookies, etc.) | Improve Setup and Running CustomersDot E2E Tests Locally |
📖 Documentation
Problem | Solutions | DRI |
---|---|---|
Documentation is sparse or outdated | Update CustomersDot E2E Test Documentation to Help Facilitate Developer Involvement |
💬 Feedback
Problem | Solutions | DRI |
---|---|---|
Test feedback occurs too late in the development cycle |
Run CustomersDot end-to-end tests per CustomersDot MR Explore Running GitLab Fulfillment E2E Tests in CustomersDot MRs Explore Running CustomersDot E2E Tests in GitLab MRs Explore Running GitLab Fulfillment E2E Tests in GitLab MRs |
⚙ Framework improvements
Problem | Solutions | DRI |
---|---|---|
Fulfillment tests in GitLab use 2 different frameworks (Chemlab + GitLab QA framework) | Migrate Chemlab E2E Tests in the GitLab Project Back to The GitLab QA Framework | |
Missing integrations in CustomersDot E2E framework that could help manual UAT efforts (ex: SFDC) | Fulfillment QE Test task - improve E2E tests efficiency |
🛠 Tooling
⚖ Test case management
Problem | Solutions | DRI |
---|---|---|
No SSoT aligning manual UAT test cases and automated E2E test cases | Improve CustomersDot Test Case Standards for Manual and Automated E2E Tests | |
Difficulties with test case organization and discoverability | Improve CustomersDot Test Case Standards for Manual and Automated E2E Tests | |
No unified standard or template for test cases | Improve CustomersDot Test Case Standards for Manual and Automated E2E Tests |