cucumber testejä lisää

tests/features/gitops-update.feature

@@ -1,15 +1,44 @@
-Feature: GitOps version update
-  As a developer
-  I want to automatically update version references in a GitOps repo
-  So that deployment is triggered with the correct artifact version
+Feature: GitOps update
+  As a GitOps repository
+  I want to update version references and report results back to the caller
+  So that the deployment chain is traceable from source to GitOps commit
 
   Background:
     Given a project repository exists in Gitea
     And a commit has been pushed to the repository
 
-  @mock @real
-  Scenario: GitOps repo receives version bump dispatch
-    When a build completes successfully and dispatches a GitOps update
-    Then the GitOps repo has a new commit with the updated version
-    And the code repo shows a gitops status link to the GitOps commit
-    And the GitOps repo shows a source status link to the code commit
+  @mock
+  Scenario: Not enough env vars — caller commit gets failure status
+    Given insufficient environment variables are provided for the GitOps update
+    When the GitOps update script runs
+    Then the caller commit shows a failure status with the missing variable name
+    And the script exits with error
+
+  @mock
+  Scenario: GitOps job fails — caller commit gets failure status
+    Given the GitOps repository clone will fail
+    When the GitOps update script runs
+    Then the caller commit shows a failure status
+    And the script exits with error
+
+  @mock
+  Scenario: Everything succeeds — caller and GitOps get success
+    Given a valid GitOps update dispatch
+    When the GitOps update script runs
+    Then the script exits successfully
+    And the caller commit shows a success status with a link to the GitOps commit
+    And the GitOps repo commit shows a success status with a link to the caller
+
+  @mock
+  Scenario: GitOps push fails — both repos get failure status
+    Given the GitOps repo push will fail after the version is committed
+    When the GitOps update script runs
+    Then the script exits with error
+    And the caller commit shows a failure status
+    And the GitOps repo commit shows a failure status linking to the caller
+
+  @mock
+  Scenario: GitOps update succeeds — this repo commit status links to caller
+    Given a valid GitOps update dispatch
+    When the GitOps update script runs
+    Then the GitOps repo commit shows a source context status linking to the caller commit