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

Add pytest test job to Gitea Actions CI workflow to gate image builds on passing tests #51

New Issue
Closed
opened 2026-03-26 08:23:28 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-26 08:23:28 +00:00
Owner
Copy Link
Copy Source

Problem

The current build.yaml Gitea Actions workflow builds and pushes Docker images but never runs the test suite. A broken backend can be built and deployed without any automated quality gate.

Task

  • Add a test job to .gitea/workflows/build.yaml (or a new test.yaml workflow file) that:
    1. Checks out the code.
    2. Sets up Python with the correct version.
    3. Installs dependencies (pip install -r requirements.txt -r requirements-dev.txt or similar).
    4. Runs pytest with appropriate flags (e.g., --tb=short -q).
  • Configure the build (image push) job to needs: [test] so it only runs when tests pass.
  • Ensure the test job works without a live Postgres instance (use mocks or SQLite if needed, or spin up a Postgres service container).

Acceptance Criteria

  • A PR with a failing test causes the CI pipeline to fail before the image is built.
  • A PR with all tests passing proceeds to build and push the image as before.
  • The workflow YAML is valid and passes act dry-run (or equivalent local check).

References

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

## Problem The current `build.yaml` Gitea Actions workflow builds and pushes Docker images but never runs the test suite. A broken backend can be built and deployed without any automated quality gate. ## Task - Add a `test` job to `.gitea/workflows/build.yaml` (or a new `test.yaml` workflow file) that: 1. Checks out the code. 2. Sets up Python with the correct version. 3. Installs dependencies (`pip install -r requirements.txt -r requirements-dev.txt` or similar). 4. Runs `pytest` with appropriate flags (e.g., `--tb=short -q`). - Configure the `build` (image push) job to `needs: [test]` so it only runs when tests pass. - Ensure the test job works without a live Postgres instance (use mocks or SQLite if needed, or spin up a Postgres service container). ## Acceptance Criteria - A PR with a failing test causes the CI pipeline to fail before the image is built. - A PR with all tests passing proceeds to build and push the image as before. - The workflow YAML is valid and passes `act` dry-run (or equivalent local check). ## References Roadmap: P2 -- CI/CD -- No test stage in the Gitea Actions workflow.
AI-Manager added the P2agent-readysmall labels 2026-03-26 08:23:28 +00:00
AI-Manager commented 2026-03-26 09:04:03 +00:00
Author
Owner
Copy Link
Copy Source

Closing: Already implemented in PR #32 (ci: add pytest and ruff linting to CI workflow). The build.yaml workflow includes a pytest test job that gates image builds.

Closing: Already implemented in PR #32 (ci: add pytest and ruff linting to CI workflow). The build.yaml workflow includes a pytest test job that gates image builds.
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 small
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#51
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?