Merge pull request #18 from elAlmani/feature/add-features-for-projects

add permission feature
elAlmani · Feb 13, 2025 · f784cdc · f784cdc
2 parents 04014f3 + 4181d4d
commit f784cdc
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/e2e/playwright-tests/features/@permissions/view-policy-violation.feature b/e2e/playwright-tests/features/@permissions/view-policy-violation.feature
@@ -5,7 +5,7 @@ Feature: VIEW_PORTFOLIO x VIEW_POLICY_VIOLATION
     Then the user opens the project with the name "test-project01"
     Then the project "policyViolations" tab should not be visible
 
-  Scenario: With VIEW_POLICY_VIOLATION Permission The User Can See The Policy Violations On Project Page
+  Scenario: With VIEW_POLICY_VIOLATION Permission The User Can See Audit View On Policy Violations Project Page
     Given the user "test-user_VP_VPV_PERMS" logs in to DependencyTrack and verifies
     Then the user navigates to "projects" page and verifies
     Then the user opens the project with the name "test-project01"

diff --git a/...ght-tests/features/@permissions/view-policy-violation_x_policy-violation-analysis.feature b/...ght-tests/features/@permissions/view-policy-violation_x_policy-violation-analysis.feature
@@ -1,13 +1,13 @@
 Feature: VIEW_PORTFOLIO x VIEW_POLICY_VIOLATION x POLICY_VIOLATION_ANALYSIS
-  Scenario: With VIEW_POLICY_VIOLATION But Without POLICY_VIOLATION_ANALYSIS Permission The User Cannot Edit The Policy Violations On Project Page
+  Scenario: With VIEW_POLICY_VIOLATION But Without POLICY_VIOLATION_ANALYSIS Permission Can See Audit View On Policy Violations Project Page But Cannot Audit Them
     Given the user "test-user_VP_VPV_PERMS" logs in to DependencyTrack and verifies
     Then the user navigates to "projects" page and verifies
     Then the user opens the project with the name "test-project01"
     Then the user navigates to project "policyViolations" tab and verifies
     Then the user expands the first violation on policy violation project tab
     Then the user verifies read access on the policy violation audit view on policy violations project tab
 
-  Scenario: With VIEW_POLICY_VIOLATION x POLICY_VIOLATION_ANALYSIS Permission The User Can Edit The Policy Violations On Project Page
+  Scenario: With VIEW_POLICY_VIOLATION x POLICY_VIOLATION_ANALYSIS Permission The User Can See Audit View On Policy Violations Project Page And Can Audit Them
     Given the user "test-user_VP_VPV_PVA_PERMS" logs in to DependencyTrack and verifies
     Then the user navigates to "projects" page and verifies
     Then the user opens the project with the name "test-project01"