leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

CI: add pytest test stage to Gitea Actions workflow that gates the image build #368

New Issue
Closed
opened 2026-03-27 16:23:55 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 16:23:55 +00:00
Owner
Copy Link
Copy Source

Problem

build.yaml builds and pushes Docker images but never runs pytest. A broken test can be shipped as a built image without any CI signal.

Work

  • Add a test job to build.yaml (or a separate test.yaml workflow) that:
    • Checks out the code.
    • Installs Python dependencies.
    • Spins up a test PostgreSQL service container.
    • Runs pytest tests/ with an appropriate exit code.
  • Make the existing build job depend on the test job (i.e., only build if tests pass).
  • Ensure environment variables needed for tests (DB URL, etc.) are provided via workflow secrets or defaults.

Acceptance Criteria

  • A failing test causes the CI run to fail before any image is built.
  • pytest output is visible in the CI logs.
  • The build job only runs after the test job succeeds.

Reference

Roadmap item: P2 CI/CD — No test stage in the Gitea Actions workflow.

## Problem `build.yaml` builds and pushes Docker images but never runs `pytest`. A broken test can be shipped as a built image without any CI signal. ## Work - Add a `test` job to `build.yaml` (or a separate `test.yaml` workflow) that: - Checks out the code. - Installs Python dependencies. - Spins up a test PostgreSQL service container. - Runs `pytest tests/` with an appropriate exit code. - Make the existing `build` job depend on the `test` job (i.e., only build if tests pass). - Ensure environment variables needed for tests (DB URL, etc.) are provided via workflow secrets or defaults. ## Acceptance Criteria - A failing test causes the CI run to fail before any image is built. - `pytest` output is visible in the CI logs. - The build job only runs after the test job succeeds. ## Reference Roadmap item: P2 CI/CD — No test stage in the Gitea Actions workflow.
AI-Manager added the P2agent-readymedium labels 2026-03-27 16:23:55 +00:00
AI-Manager commented 2026-03-27 17:06:22 +00:00
Author
Owner
Copy Link
Copy Source

[Triage] Already implemented in main. Both .gitea/workflows/test.yaml and build.yaml include pytest test stages that gate the build. Closing as resolved.

[Triage] Already implemented in main. Both .gitea/workflows/test.yaml and build.yaml include pytest test stages that gate the build. Closing as resolved.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#368
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?