Add E2E test for compliance framework report
Description of the test
A new E2E test for the compliance framework report.
- Includes a new ComplianceFramework resource
- Adds a graphQL mutation to add a compliance framework to a project
- Adds QA selectors to the Compliance Framework Report Vue files
See gitlab-org/quality/testcases#4003 (closed) New testcase: https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/396600
Tasks
-
Remove the feature flag after !114790 (merged) is merged
How to set up and validate locally
From the qa
directory, assuming you have a GitLab instance running at http://gdk.test:3000
:
bundle exec bin/qa Test::Instance::All http://gdk.test:3000 -- qa/specs/features/ee/browser_ui/10_govern/group/compliance_framework_report_spec.rb
Checklist
-
Confirm the test has a testcase:
tag linking to an existing test case in the test case project. -
Note if the test is intended to run in specific scenarios. If a scenario is new, add a link to the MR that adds the new scenario. -
Follow the end-to-end tests style guide and best practices. -
Use the appropriate RSpec metadata tag(s). - Most resources will be cleaned up via the general cleanup task. Check that is successful, or ensure resources are cleaned up in the test:
-
New resources have api_get_path
andapi_delete_path
implemented if possible. -
If any resource cannot be deleted in the general delete task, make sure it is ignored. -
If any resource cannot be deleted in the general delete task, remove it in the test (e.g., in an after
block).
-
-
Ensure that no transient bugs are hidden accidentally due to the usage of waits
andreloads
. -
Verify the tags to ensure it runs on the desired test environments. -
If this MR has a dependency on another MR, such as a GitLab QA MR, specify the order in which the MRs should be merged. -
(If applicable) Create a follow-up issue to document the special setup necessary to run the test: ISSUE_LINK -
If the test requires an admin's personal access token, ensure that the test passes on your local environment with and without the GITLAB_QA_ADMIN_ACCESS_TOKEN
provided.
Edited by Mark Lapierre