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

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

Context

build.yaml in the Gitea Actions workflow builds and pushes Docker images but never runs the test suite. A failing test can be merged and shipped without any signal.

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

What to do

  • Add a test job to .gitea/workflows/build.yaml (or create a separate test.yaml).
  • The job should: check out the code, install Python dependencies, and run pytest.
  • Gate the build/push job on the test job passing (needs: test).
  • Cache pip dependencies for faster runs.

Acceptance criteria

  • A failed pytest run causes the CI pipeline to fail before any image is built or pushed.
  • A passing pytest run allows the build/push job to proceed.
  • The test job appears in the Gitea Actions UI.
## Context `build.yaml` in the Gitea Actions workflow builds and pushes Docker images but never runs the test suite. A failing test can be merged and shipped without any signal. Roadmap reference: ROADMAP.md > P2 > CI/CD > No test stage in the Gitea Actions workflow ## What to do - Add a `test` job to `.gitea/workflows/build.yaml` (or create a separate `test.yaml`). - The job should: check out the code, install Python dependencies, and run `pytest`. - Gate the build/push job on the test job passing (`needs: test`). - Cache pip dependencies for faster runs. ## Acceptance criteria - A failed `pytest` run causes the CI pipeline to fail before any image is built or pushed. - A passing `pytest` run allows the build/push job to proceed. - The test job appears in the Gitea Actions UI.
AI-Manager added the P2agent-readysmall labels 2026-03-27 05:24:12 +00:00
AI-Manager commented 2026-03-27 06:05:11 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved in the current codebase.

Both .gitea/workflows/test.yaml and build.yaml include a pytest step that runs python3 -m pytest tests/ -v --tb=short -x with appropriate environment variables. The build workflow gates image builds on test success via needs: test.

Closing as already implemented.

This issue has already been resolved in the current codebase. Both `.gitea/workflows/test.yaml` and `build.yaml` include a pytest step that runs `python3 -m pytest tests/ -v --tb=short -x` with appropriate environment variables. The build workflow gates image builds on test success via `needs: test`. Closing as already implemented.
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#216
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?