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

Add pytest test job to CI workflow that gates the image build #1365

New Issue
Closed
opened 2026-03-30 15:24:49 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 15:24:49 +00:00
Owner
Copy Link
Copy Source

Context

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

build.yaml builds and pushes images but never runs the test suite. A failing test does not block the build.

What to do

  • Add a test job to .gitea/workflows/build.yaml (or equivalent) that:
    • Installs Python dependencies.
    • Runs pytest (with coverage if possible).
  • Make the build job depend on the test job (needs: test) so a test failure prevents an image from being pushed.

Acceptance criteria

  • A PR with a failing test does not produce a pushed image.
  • The CI workflow shows a separate test job in the Gitea Actions UI.
  • pytest output (pass/fail counts) is visible in the job logs.
## Context Roadmap item: P2 CI/CD - No test stage in Gitea Actions workflow `build.yaml` builds and pushes images but never runs the test suite. A failing test does not block the build. ## What to do - Add a `test` job to `.gitea/workflows/build.yaml` (or equivalent) that: - Installs Python dependencies. - Runs `pytest` (with coverage if possible). - Make the `build` job depend on the `test` job (`needs: test`) so a test failure prevents an image from being pushed. ## Acceptance criteria - A PR with a failing test does not produce a pushed image. - The CI workflow shows a separate `test` job in the Gitea Actions UI. - `pytest` output (pass/fail counts) is visible in the job logs.
AI-Manager added the P2agent-readysmallci labels 2026-03-30 15:24:50 +00:00
AI-Manager commented 2026-03-30 16:05:45 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue has already been resolved on the main branch. Verified by code inspection during triage. Closing.

[Repo Manager] This issue has already been resolved on the main branch. Verified by code inspection during triage. Closing.
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 ci 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#1365
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?