niko/gitea-ci-library
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

clean up
CI Feature / Load example-gitea-env.conf to pipeline env (push) Successful in 20s
Details
acc-tests Cucumber test report
Details
CI Feature / Cucumber tests (push) Failing after 26s
Details
unit-tests Bats test report
Details
CI Feature / Bats tests (push) Failing after 1m25s
Details
CI Feature / Report Summary (push) Successful in 5s
Details

Browse Source
This commit is contained in:
moilanik
2026-06-22 06:57:09 +03:00
parent f58497f5e8
commit 84978784fe
6 changed files with 76 additions and 328 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/features/gitops-update.feature
+14 -16
View File
@@ -1,6 +1,6 @@
Feature: GitOps update
As a GitOps repository
I want to update version references and report results back to the caller
I want to update version references and report results to the caller
So that the deployment chain is traceable from source to GitOps commit
Background:
@@ -8,37 +8,35 @@ Feature: GitOps update
And a commit has been pushed to the repository
@mock
Scenario: Not enough env vars — caller commit gets failure status
Scenario: Not enough env vars — script fails, no status set
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
Then the script exits with error
@mock
Scenario: GitOps job fails — caller commit gets failure status
Scenario: GitOps job fails — no status set (SHA not yet known)
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
Then the script exits with error
@mock
Scenario: Everything succeeds — caller and GitOps get success
Scenario: Everything succeeds — GitOps repo gets success status with link to caller
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
And the GitOps repo commit shows a success status with a link to the caller commit
@mock
Scenario: GitOps push fails — both repos get failure status
Scenario: GitOps push fails — GitOps repo gets 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
And the GitOps repo commit shows a failure status linking to the caller commit
@mock
Scenario: GitOps update succeeds — this repo commit status links to caller
Given a valid GitOps update dispatch
Scenario: No changes — GitOps repo gets "no change" status
Given the version file already has the target version
When the GitOps update script runs
Then the GitOps repo commit shows a source context status linking to the caller commit
Then the script exits successfully
And the GitOps repo commit shows a "no change" status
And no Git commit or push was performed