test: remove workflow policy assertions #69

Merged

Wuast94 merged 3 commits from codex/remove-workflow-policy-tests into main 2026-06-19 15:15:20 +02:00

Conversation 0 Commits 3 Files changed 7 +89 -385

Wuast94 commented 2026-06-19 13:06:01 +02:00

Owner

Copy link

What

Remove Dependency-Track workflow/docs/version policy assertions from internal/ci tests. Keep the actual SBOM generation and upload-script behavior tests.

Fix Forgejo E2E by running the test process as a Compose service on the same Docker network as Uptime Kuma. The CI job no longer depends on host 127.0.0.1:3001 port publishing from the Forgejo runner environment.

Also fix scripts/run-e2e.sh readiness failure handling so it reports the real curl exit code and does not continue into go test after readiness timeout.

Why

The failing TestForgejoDependencyTrackWorkflowPolicy is a YAML policy assertion, not application logic. The E2E failure showed the runner could start a healthy Uptime Kuma container but could not reach its published host port. Running E2E on the Compose network targets the real service name uptime-kuma:3001.

Verification

• just format
• ./scripts/devcontainer-run.sh go test ./internal/ci -run 'TestE2ERunner|TestDockerComposeE2E|TestGenerateSBOM|TestDependencyTrackUpload' -count=1 -v\n- Host Compose E2E: docker compose -p ci-pr-verify -f docker-compose.yaml up -d --wait --wait-timeout 120 uptime-kuma && docker compose -p ci-pr-verify -f docker-compose.yaml run --rm e2e-runner\n- just everything

## What Remove Dependency-Track workflow/docs/version policy assertions from internal/ci tests. Keep the actual SBOM generation and upload-script behavior tests. Fix Forgejo E2E by running the test process as a Compose service on the same Docker network as Uptime Kuma. The CI job no longer depends on host `127.0.0.1:3001` port publishing from the Forgejo runner environment. Also fix `scripts/run-e2e.sh` readiness failure handling so it reports the real curl exit code and does not continue into `go test` after readiness timeout. ## Why The failing `TestForgejoDependencyTrackWorkflowPolicy` is a YAML policy assertion, not application logic. The E2E failure showed the runner could start a healthy Uptime Kuma container but could not reach its published host port. Running E2E on the Compose network targets the real service name `uptime-kuma:3001`. ## Verification - `just format` - `./scripts/devcontainer-run.sh go test ./internal/ci -run 'TestE2ERunner|TestDockerComposeE2E|TestGenerateSBOM|TestDependencyTrackUpload' -count=1 -v`\n- Host Compose E2E: `docker compose -p ci-pr-verify -f docker-compose.yaml up -d --wait --wait-timeout 120 uptime-kuma && docker compose -p ci-pr-verify -f docker-compose.yaml run --rm e2e-runner`\n- `just everything`

Wuast94 added 1 commit 2026-06-19 13:06:01 +02:00

test: remove workflow policy assertions 3a864b2a50

Wuast94 added 1 commit 2026-06-19 13:25:34 +02:00

fix: run e2e inside compose network 1f441480f9

Wuast94 added 1 commit 2026-06-19 15:07:52 +02:00

fix: build e2e runner image 7b19b61a6b

Wuast94 merged commit 48111d76a4 into main 2026-06-19 15:15:20 +02:00

Wuast94 deleted branch codex/remove-workflow-policy-tests 2026-06-19 15:15:20 +02:00

Wuast94 referenced this pull request from a commit 2026-06-19 15:15:21 +02:00

Merge pull request 'test: remove workflow policy assertions' (#69) from codex/remove-workflow-policy-tests into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Wuast94/kumaste!69

No description provided.