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

New Issue
Closed
opened 2026-03-29 09:25:02 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 09:25:02 +00:00
Owner
Copy Link
Copy Source

Background

build.yaml builds and pushes Docker images but never runs the test suite. A broken backend can be shipped as a valid image.

Task

  1. Add a test job to .gitea/workflows/build.yaml (or a new test.yaml workflow).
  2. The job should: check out code, install Python dependencies, and run pytest.
  3. The build/push job should depend on (or be gated by) the test job passing.

Acceptance Criteria

  • Every push/PR triggers pytest in CI.
  • A failing test prevents the image from being built and pushed.
  • The test job is visible in the Gitea Actions UI.

Reference

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

## Background `build.yaml` builds and pushes Docker images but never runs the test suite. A broken backend can be shipped as a valid image. ## Task 1. Add a `test` job to `.gitea/workflows/build.yaml` (or a new `test.yaml` workflow). 2. The job should: check out code, install Python dependencies, and run `pytest`. 3. The build/push job should depend on (or be gated by) the test job passing. ## Acceptance Criteria - [ ] Every push/PR triggers pytest in CI. - [ ] A failing test prevents the image from being built and pushed. - [ ] The test job is visible in the Gitea Actions UI. ## Reference Roadmap: P2 CI/CD -- No test stage in the Gitea Actions workflow.
AI-Manager added the P2agent-readysmallinfra labels 2026-03-29 09:25:02 +00:00
AI-Manager commented 2026-03-29 10:04:35 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager. This issue has already been resolved. The CI workflow (.gitea/workflows/build.yaml) includes a test job that runs python3 -m pytest tests/ -v --tb=short -x with appropriate environment variables. The build-api and build-frontend jobs depend on the test job passing. Closing as already implemented.

Triaged by repo manager. This issue has already been resolved. The CI workflow (`.gitea/workflows/build.yaml`) includes a `test` job that runs `python3 -m pytest tests/ -v --tb=short -x` with appropriate environment variables. The `build-api` and `build-frontend` jobs depend on the test job passing. 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 infra 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#954
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?