E2E: Migrate Growth Stage Pages to Use data-testids

What does this MR do and why?

Relates to gitlab-org/quality/quality-engineering/team-tasks#1837 (closed)

This MR migrates the QA pages and frontend components related to sectiongrowth from data-qa-selectors to data-testids, while also removing any related unused data-qa-selectors.

These changes should only affect the following E2E tests:

  • qa/qa/specs/features/ee/browser_ui/15_growth/free_trial_spec.rb
  • qa/qa/specs/features/ee/browser_ui/11_fulfillment/saas_user_limit_experience_spec.rb

How to set up and validate locally

If you would like to run these tests locally, you will need to make some adjustments to the tests and have a local CustomersDot instance installed and configured to work with your GDK.

  1. Ensure your GDK is set up to simulate a SaaS instance, ex:

In env.runit:

export GITLAB_SIMULATE_SAAS=true

In gdk.yml:

license:
  customer_portal_url: http://localhost:5000
  1. In qa/qa/specs/features/ee/browser_ui/15_growth/free_trial_spec.rb, remove the only: { subdomain: :staging } tag
  2. Add the following in the before block after line 73: group_for_trial.add_member(user, Resource::Members::AccessLevel::OWNER)
  3. From the qa directory, run
GITLAB_QA_ADMIN_ACCESS_TOKEN=<gdk admin PAT> GITLAB_INITIAL_ROOT_PASSWORD=<gdk root password> QA_GITLAB_URL=<gdk url and port> WEBDRIVER_HEADLESS=false bundle exec rspec qa/specs/features/ee/browser_ui/15_growth/free_trial_spec.rb:72

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Valerie Burton

Merge request reports

Loading