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 #417

New Issue
Closed
opened 2026-03-27 18:24:53 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 18:24:53 +00:00
Owner
Copy Link
Copy Source

Summary

build.yaml builds and pushes Docker images but never runs pytest. Broken tests can be silently shipped.

What to do

  1. Add a test job in build.yaml (or a separate test.yaml workflow) that:
    • Sets up Python
    • Installs dependencies (pip install -r requirements.txt and test deps)
    • Starts a test PostgreSQL service container
    • Runs pytest tests/ with coverage reporting
  2. Make the build job needs: [test] so images are only built when tests pass
  3. Optionally upload a coverage report as a workflow artifact

Acceptance Criteria

  • A failing test causes the CI pipeline to fail before any image is built or pushed
  • The test job runs on every push and pull request to main
  • pytest output is visible in the CI run logs

Reference

Roadmap: P2 - CI/CD / No test stage

## Summary `build.yaml` builds and pushes Docker images but never runs `pytest`. Broken tests can be silently shipped. ## What to do 1. Add a `test` job in `build.yaml` (or a separate `test.yaml` workflow) that: - Sets up Python - Installs dependencies (`pip install -r requirements.txt` and test deps) - Starts a test PostgreSQL service container - Runs `pytest tests/` with coverage reporting 2. Make the `build` job `needs: [test]` so images are only built when tests pass 3. Optionally upload a coverage report as a workflow artifact ## Acceptance Criteria - A failing test causes the CI pipeline to fail before any image is built or pushed - The test job runs on every push and pull request to `main` - `pytest` output is visible in the CI run logs ## Reference Roadmap: P2 - CI/CD / No test stage
AI-Manager added the P2agent-readysmall labels 2026-03-27 18:24:53 +00:00
AI-Manager commented 2026-03-27 19:06:11 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already Implemented

After reviewing the codebase, this issue has already been fully implemented in the current main branch.

This issue can be closed.

## Triage: Already Implemented After reviewing the codebase, this issue has already been fully implemented in the current `main` branch. This issue can be closed.
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#417
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?