E2E: Migrate Trial Specs from Chemlab to GitLab E2E Framework
What does this MR do and why?
Relates to:
- gitlab-org/quality/quality-engineering/team-tasks#2641 (closed)
- gitlab-org/quality/quality-engineering/team-tasks#2640 (closed)
This MR is part of a larger effort Migrate Chemlab E2E Tests in the GitLab Project Back to The GitLab E2E Framework
- Migrates
Gitlab::Page::Trials::New
andGitlab::Page::Trials::Select
to GitLab E2E pagesQA::EE::Page::Trials::New
andQA::EE::Page::Trials::Select
, respectively - Removes
QA::Page::Alert::FreeTrial
and moves to a new moduleQA::EE::Page::Alert::FreeTrial
, which is prepended toQA::Page::Group::Show
since this alert displays in the context of the group page. This was kept as a separate alert module since this can also display on a user's profile billing page, if an individual trial is selected instead. - Moves
QA::Flow::Trial
toQA::EE::Flow::Trial
, since the pages it uses are in the context of EE as well. - Updates
saas_user_limit_experience_spec
,free_trial_spec
andQA::EE::Flow::Trial
methods to use these new pages - Updates the
data-testid
s to follow the GitLab E2E framework's style guidelines - Updates any affected frontend specs that share these
data-testid
s - Removes old Chemlab pages, stubs and dependencies that are no longer in use (ex:
Chemlab::Vendor::GitlabHandbook::Page::About
, since about.staging.gitlab.com has been deprecated)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
How to set up and validate locally
The tests that use these pages are only configured to run against staging.gitlab.com at this time. There are quite a few workarounds needed in order to try and run parts of these tests locally. If you would like to validate any of the changes locally, please let me know and I can try to help guide you through how to do so.
Edited by Valerie Burton