Add feature specs for Security Configuration page
Why are we doing this work
The Security Configuration page is receiving lots of changes as part of &4787, and also extended via &4908 (closed) and #263251 (closed).
In order to support this and ease future work, we'll refactor the page on both the frontend and backend. (See #322624 (closed).)
To increase confidence in these changes/refactorings, we should add feature tests for basic functionality/presentation.
Finally, this is only about adding specs for GitLab Ultimate behaviour. While the Core page is currently a completely separate implementation, the eventual goal is to make these share as much code as possible. Writing feature specs for both I think might violate the guidelines laid out in the docs.
Relevant links
Non-functional requirements
- [-] Documentation:
- [-] Feature flag:
- [-] Performance:
-
Testing: That's the only goal of this issue! More tests.
Implementation plan
-
frontend Create spec at ee/spec/features/projects/security/configuration_spec.js
- Only test minimal happy path for GitLab Ultimate:
-
That SAST configuration button UI is visible -
That SAST status is rendered as expected
-
- Only test minimal happy path for GitLab Ultimate:
Edited by Mark Florian