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

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

Problem

build.yaml builds and pushes Docker images without ever running the test suite. A broken build can be pushed and deployed without any automated quality gate.

Work

  • Add a test job to .gitea/workflows/build.yaml that runs before the build job.
  • The test job should:
    • Check out the code.
    • Install Python dependencies (pip install -r requirements.txt).
    • Start a test PostgreSQL service (use the Gitea Actions services key or docker compose up -d db).
    • Run pytest tests/ with appropriate environment variables.
  • Make the build job needs: test so a test failure prevents the image from being pushed.

Acceptance Criteria

  • A failing test prevents the Docker image from being built/pushed.
  • The CI log shows pytest output.
  • A passing test suite allows the build to proceed.

Reference

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

## Problem `build.yaml` builds and pushes Docker images without ever running the test suite. A broken build can be pushed and deployed without any automated quality gate. ## Work - Add a `test` job to `.gitea/workflows/build.yaml` that runs before the `build` job. - The test job should: - Check out the code. - Install Python dependencies (`pip install -r requirements.txt`). - Start a test PostgreSQL service (use the Gitea Actions `services` key or `docker compose up -d db`). - Run `pytest tests/` with appropriate environment variables. - Make the `build` job `needs: test` so a test failure prevents the image from being pushed. ## Acceptance Criteria - A failing test prevents the Docker image from being built/pushed. - The CI log shows pytest output. - A passing test suite allows the build to proceed. ## Reference Roadmap item: P2 CI/CD — No test stage in the Gitea Actions workflow.
AI-Manager added the P2agent-readymedium labels 2026-03-27 14:23:04 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-27 15:02:48 +00:00
AI-Manager commented 2026-03-27 15:05:08 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue is resolved. .gitea/workflows/build.yaml has a test job that installs dependencies, runs pytest with proper env vars, and gates the build jobs behind it.

[Repo Manager] This issue is resolved. .gitea/workflows/build.yaml has a test job that installs dependencies, runs pytest with proper env vars, and gates the build jobs behind it.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#345
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?