Fix for Fulfillment specs that use go_to_groups
What does this MR do and why?
Describe in detail what your merge request does and why.
Fix for
- #403589 (closed)
- #403589 (closed)
- #403588 (closed)
- #403587 (closed)
- #403586 (closed)
- #403585 (closed)
- #403584 (closed)
- #403592 (closed)
In which when the test was in a group, when calling go_to_group
it needed to use previous functionality of that function that changed in !115169 (diffs)
This MR allows for the new functionality when found, otherwise fallback to previous go_to_group
functionality
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
See above issues, test is in a group trying to access a group.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Run fulfillment tests against staging eg.
GITLAB_USERNAME=<username> GITLAB_PASSWORD=<password> WEBDRIVER_HEADLESS=false GITLAB_QA_USER_AGENT=<agent> GITLAB_ADMIN_USERNAME=<admin_user> GITLAB_ADMIN_PASSWORD=<password> GITLAB_QA_ACCESS_TOKEN=<token> GITLAB_QA_ADMIN_ACCESS_TOKEN=<token> QA_DEBUG=true bundle exec bin/qa Test::Instance::All https://staging.gitlab.com qa/specs/features/ee/browser_ui/11_fulfillment/purchase/overage_modal_spec.rb
Also run tests that use this function eg.
GITLAB_USERNAME=<username> GITLAB_PASSWORD=<password> WEBDRIVER_HEADLESS=false GITLAB_QA_USER_AGENT=<agent> GITLAB_ADMIN_USERNAME=<admin_user> GITLAB_ADMIN_PASSWORD=<password> GITLAB_QA_ACCESS_TOKEN=<token> GITLAB_QA_ADMIN_ACCESS_TOKEN=<token> QA_DEBUG=true bundle exec bin/qa Test::Instance::All https://staging.gitlab.com qa/specs/features/ee/browser_ui/3_create/repository/project_templates_spec.rb
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.