Explore Running GitLab Fulfillment E2E Tests in GitLab MRs
There is currently no way to verify GitLab changes with most Fulfillment E2E tests in the GitLab project until the changes hit Staging, where it can often be too late to catch any bugs before they make it to production. This also places most of the responsibility on Fulfillment SETs to update stale tests, rather than having developers take care of these changes in their MRs earlier in the process.
Some tests can be modified to run locally (if you have a local CustomersDot setup), but this is very difficult and time consuming to do and most non-Fulfillment engineers would not have this setup in place.
Note: There is already a plan in place to implement this for CustomersDot E2E tests: gitlab-org/customers-gitlab-com#4384 (closed). This issue is to discuss how / if we can do something similar for the Fulfillment tests in GitLab.
Proposal
This issue should be used to explore how we can run the GitLab Fulfillment E2E tests located in qa/qa/specs/features/ee/browser_ui/11_fulfillment
against a GitLab instance (containing the changes from a GitLab MR) integrated with a CustomersDot instance (relies on containerization work being completed in Run CustomersDot end-to-end tests per Customers... (gitlab-org/customers-gitlab-com#4384 - closed) first)