Update for security_reports_spec
What does this MR do?
Updates the security_reports_spec
for the group Dashboard which was changed
- A new dashboard containing high level details was added
- The old dashboard was moved to Vulnerability Report
Engineering ticket - #227878 (closed)
QA ticket to work on E2E test - gitlab-org/quality/testcases#950 (closed)
Failure in master when this change was rolled out - #235804 (closed)
Screenshots
See #235804 (closed) for the new dashboard
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
/closes #235804 (closed) /closes gitlab-org/quality/testcases#950 (closed)
Edited by Will Meek