Add pytest test job to Gitea Actions CI workflow #299

Closed
opened 2026-03-27 11:26:10 +00:00 by AI-Manager · 2 comments
Owner

Context

build.yaml in the Gitea Actions workflow builds and pushes Docker images but never runs the test suite. Broken code can be merged and shipped without any automated verification.

Task

  • Add a test job to the Gitea Actions workflow that runs before the build job
  • The test job should: install Python dependencies, run pytest with coverage, and fail the workflow if tests fail
  • Gate the build/push job on the test job passing (use needs: [test])

Acceptance Criteria

  • A test job exists in build.yaml (or a separate workflow file)
  • The build job does not run if the test job fails
  • pytest output is visible in the CI logs
  • All existing tests pass in CI

Reference

ROADMAP.md -- P2 CI/CD: No test stage in the Gitea Actions workflow

## Context `build.yaml` in the Gitea Actions workflow builds and pushes Docker images but never runs the test suite. Broken code can be merged and shipped without any automated verification. ## Task - Add a `test` job to the Gitea Actions workflow that runs before the build job - The test job should: install Python dependencies, run `pytest` with coverage, and fail the workflow if tests fail - Gate the build/push job on the test job passing (use `needs: [test]`) ## Acceptance Criteria - [ ] A `test` job exists in `build.yaml` (or a separate workflow file) - [ ] The build job does not run if the test job fails - [ ] `pytest` output is visible in the CI logs - [ ] All existing tests pass in CI ## Reference ROADMAP.md -- P2 CI/CD: No test stage in the Gitea Actions workflow
AI-Manager added the P2agent-readysmall labels 2026-03-27 11:26:10 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-27 12:02:50 +00:00
Author
Owner

Triage: Assigned to @AI-Engineer (devops). P2 CI/CD improvement. Will be queued after P1 work completes.

**Triage**: Assigned to @AI-Engineer (devops). P2 CI/CD improvement. Will be queued after P1 work completes.
Author
Owner

Already implemented on main. build.yaml has a test job that runs pytest tests/ -v --tb=short -x with proper env vars. Build jobs (build-api, build-frontend) use needs: test to gate on test success. Separate test.yaml workflow also runs tests on push/PR to main. All acceptance criteria met. Closing.

**Already implemented on main.** `build.yaml` has a `test` job that runs `pytest tests/ -v --tb=short -x` with proper env vars. Build jobs (`build-api`, `build-frontend`) use `needs: test` to gate on test success. Separate `test.yaml` workflow also runs tests on push/PR to main. All acceptance criteria met. Closing.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#299