## Summary This issue tracks the development of end-to-end (E2E) tests for the Group Level Secrets feature in GitLab Secrets Manager. The tests will validate group-level secret management functionality, including permissions, access control, and CI/CD integration. Since we can reuse much of the existing project secrets manager implementation, this effort is significantly reduced compared to the initial project-level E2E tests ([&18849](https://gitlab.com/groups/gitlab-org/-/epics/18849)). We don't need to worry about deploying tests in GDK or CNG, which streamlines the workload. **Total Estimated Effort:** 8 story points ## Implementation Plan Based on [@srajadas](https://gitlab.com/srajadas)'s breakdown, the following test scenarios need to be implemented: ### 1. Enable group secrets manager and verify default owner permissions are present **Weight:** 2 - Verify group secrets manager can be enabled at the group level - Confirm default owner permissions are correctly assigned - Validate initial state and configuration ### 2. Add group secret permissions **Weight:** 2 - Test adding various permission levels for group secrets - Verify permission inheritance and assignment - Validate permission management UI/API functionality ### 3. Verify access control during group secrets CRUD operations **Weight:** 3 - Test Create, Read, Update, Delete operations for group secrets - Validate access control enforcement across different user roles - Ensure unauthorized users cannot perform restricted operations - Test edge cases and permission boundaries ### 4. Access group secrets in CI pipeline **Weight:** 2 - Verify group secrets are accessible in CI/CD pipelines - Test secret injection and usage in pipeline jobs - Validate security and isolation of secrets during pipeline execution --- <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=574063) </details>