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

New Issue
Closed
opened 2026-03-29 01:23:39 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-29 01:23:39 +00:00
Owner
Copy Link
Copy Source

Background

build.yaml builds and pushes Docker images but never runs pytest. Test failures are not caught in CI, so broken code can be merged and built.

What to do

  1. Add a test job to .gitea/workflows/build.yaml (or a new test.yaml) that:
    • Sets up Python and installs dependencies
    • Runs pytest tests/ with coverage output
  2. Make the build job depend on test so images are only built when tests pass
  3. (Optional) Upload coverage report as a CI artifact

Acceptance criteria

  • A failing test blocks the build job
  • pytest output is visible in the CI run log
  • A passing test suite allows the build and push to proceed normally
  • The workflow runs on both push and pull_request events

References

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

## Background `build.yaml` builds and pushes Docker images but never runs `pytest`. Test failures are not caught in CI, so broken code can be merged and built. ## What to do 1. Add a `test` job to `.gitea/workflows/build.yaml` (or a new `test.yaml`) that: - Sets up Python and installs dependencies - Runs `pytest tests/` with coverage output 2. Make the `build` job depend on `test` so images are only built when tests pass 3. (Optional) Upload coverage report as a CI artifact ## Acceptance criteria - A failing test blocks the build job - `pytest` output is visible in the CI run log - A passing test suite allows the build and push to proceed normally - The workflow runs on both push and pull_request events ## References Roadmap item: P2 CI/CD -- No test stage in the Gitea Actions workflow
AI-Manager added the P2agent-readysmalltest labels 2026-03-29 01:23:39 +00:00
AI-Manager commented 2026-03-29 02:06:23 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved and merged into main via PR #32 (ci: add pytest and ruff linting to CI workflow). Closing as completed.

This issue has already been resolved and merged into main via PR #32 (ci: add pytest and ruff linting to CI workflow). Closing as completed.
AI-Manager commented 2026-03-29 02:07:17 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved and merged into main via PR #32 (ci: add pytest and ruff linting to CI workflow). Closing as completed.

This issue has already been resolved and merged into main via PR #32 (ci: add pytest and ruff linting to CI workflow). Closing as completed.
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 test
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#814
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?