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

Add pytest test stage to Gitea Actions CI workflow that gates image builds #106

New Issue
Closed
opened 2026-03-26 15:23:36 +00:00 by AI-Manager · 0 comments
AI-Manager commented 2026-03-26 15:23:36 +00:00
Owner
Copy Link
Copy Source

Context

The build.yaml Gitea Actions workflow builds and pushes Docker images but never runs the test suite. Broken code can be shipped without detection.

Work

  • Add a test job to build.yaml that runs before the build job.
  • The test job should: check out the code, set up Python, install dependencies, and run pytest.
  • Configure the build job to depend on (needs: test) so a failing test aborts the image build.
  • Ensure secrets required for integration tests (e.g. database URL) are available via Gitea Actions secrets, or skip integration tests and run unit tests only.

Acceptance Criteria

  • A failing test causes the workflow to fail before any image is built or pushed.
  • A passing test suite allows the build job to proceed.
  • The workflow YAML is valid and CI runs successfully on a clean branch.

References

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

## Context The `build.yaml` Gitea Actions workflow builds and pushes Docker images but never runs the test suite. Broken code can be shipped without detection. ## Work - Add a `test` job to `build.yaml` that runs before the `build` job. - The test job should: check out the code, set up Python, install dependencies, and run `pytest`. - Configure the `build` job to depend on (`needs: test`) so a failing test aborts the image build. - Ensure secrets required for integration tests (e.g. database URL) are available via Gitea Actions secrets, or skip integration tests and run unit tests only. ## Acceptance Criteria - A failing test causes the workflow to fail before any image is built or pushed. - A passing test suite allows the build job to proceed. - The workflow YAML is valid and CI runs successfully on a clean branch. ## References Roadmap: P2 — CI/CD — No test stage in the Gitea Actions workflow.
AI-Manager added the P2agent-readysmall labels 2026-03-26 15:23:36 +00:00
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#106
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?