Update locator for group save-permissions-changes-button
What does this MR do and why?
Updating a locator for saving group permissions settings as it was changed in !139120 (merged), but not changed in the method that is being updated in this MR.
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.
Screenshots or screen recordings
N/A. Only updating locator that was changed before.
How to set up and validate locally
N/A. Only updating locator that was changed before.
Merge request reports
Activity
assigned to @ichernikov
changed milestone to %16.8
added QA maintenancerefactor typemaintenance labels
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer QA @AndyWH
(UTC-8, 8 hours behind author)
@treagitlab
(UTC+0, same timezone as author)
Please check reviewer's status!
Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangeradded test label
added teamTest Engineering label
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for d9b38b3cexpand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Verify | 31 | 0 | 0 | 0 | 31 | ✅ | | Govern | 72 | 0 | 0 | 0 | 72 | ✅ | | Data Stores | 23 | 0 | 0 | 0 | 23 | ✅ | | Package | 15 | 0 | 1 | 0 | 16 | ✅ | | Plan | 55 | 0 | 0 | 0 | 55 | ✅ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | | Create | 54 | 0 | 7 | 0 | 61 | ✅ | | Monitor | 7 | 0 | 0 | 0 | 7 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Manage | 0 | 0 | 1 | 0 | 1 | ➖ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 264 | 0 | 9 | 0 | 273 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-package-and-test:
test report for d9b38b3cexpand test summary
+---------------------------------------------------------------------+ | suites summary | +----------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +----------------+--------+--------+---------+-------+-------+--------+ | Govern | 286 | 0 | 20 | 10 | 306 | ✅ | | Plan | 241 | 0 | 10 | 3 | 251 | ✅ | | Create | 534 | 0 | 63 | 8 | 597 | ✅ | | Fulfillment | 8 | 0 | 69 | 0 | 77 | ✅ | | ModelOps | 0 | 0 | 6 | 0 | 6 | ➖ | | Systems | 8 | 0 | 0 | 0 | 8 | ✅ | | Package | 226 | 0 | 15 | 0 | 241 | ✅ | | Verify | 138 | 0 | 27 | 6 | 165 | ✅ | | Release | 15 | 0 | 3 | 0 | 18 | ✅ | | Manage | 40 | 0 | 10 | 4 | 50 | ✅ | | GitLab Metrics | 2 | 0 | 1 | 0 | 3 | ✅ | | Analytics | 7 | 0 | 0 | 0 | 7 | ✅ | | Data Stores | 115 | 0 | 1 | 0 | 116 | ✅ | | Configure | 1 | 0 | 9 | 0 | 10 | ✅ | | Monitor | 28 | 0 | 13 | 0 | 41 | ✅ | | Secure | 5 | 1 | 3 | 0 | 9 | ❌ | | Growth | 0 | 0 | 6 | 0 | 6 | ➖ | +----------------+--------+--------+---------+-------+-------+--------+ | Total | 1654 | 1 | 256 | 31 | 1911 | ❌ | +----------------+--------+--------+---------+-------+-------+--------+
Edited by Ghost Useradded Quality label
@acunskis, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 4 hours ago, you should:
- Ensure the merge request is not in Draft status.
- Start a pipeline (especially important for Community contribution merge requests).
- Set the merge request to auto-merge.
This is a guideline, not a rule. Please consider replying to this comment for transparency.
This message was generated automatically. You're welcome to improve it.
mentioned in commit c36fe6c5
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label