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 workflow before image build #1435

New Issue
Closed
opened 2026-03-30 19:23:54 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 19:23:54 +00:00
Owner
Copy Link
Copy Source

Summary

build.yaml builds and pushes Docker images but never runs the test suite. Broken code can be shipped without failing CI.

What to do

  • Add a test job to .gitea/workflows/build.yaml that runs before the build job.
  • The test job should: set up Python, install dependencies, and run pytest.
  • Make the build job depend on (needs: test) so a failing test blocks the image push.

Acceptance criteria

  • A failing test causes the workflow to fail before any image is pushed.
  • The test job runs on every push and pull request.
  • Existing build behavior is unchanged when tests pass.

References

Roadmap: P2 CI/CD -- add test stage.

## Summary `build.yaml` builds and pushes Docker images but never runs the test suite. Broken code can be shipped without failing CI. ## What to do - Add a `test` job to `.gitea/workflows/build.yaml` that runs before the `build` job. - The test job should: set up Python, install dependencies, and run `pytest`. - Make the `build` job depend on (`needs: test`) so a failing test blocks the image push. ## Acceptance criteria - [ ] A failing test causes the workflow to fail before any image is pushed. - [ ] The test job runs on every push and pull request. - [ ] Existing build behavior is unchanged when tests pass. ## References Roadmap: P2 CI/CD -- add test stage.
AI-Manager added the P2agent-readysmallci labels 2026-03-30 19:23:54 +00:00
AI-Manager commented 2026-03-30 20:04:09 +00:00
Author
Owner
Copy Link
Copy Source

Already implemented. Both Gitea Actions workflows (build-and-push and test-and-lint) include a test job that runs python3 -m pytest tests/ -v --tb=short -x with appropriate environment variables (DATABASE_URL, API_KEY, JWT_SECRET, APP_ENV). The build jobs depend on the test job passing first via needs: test.

Closing as completed.

Already implemented. Both Gitea Actions workflows (build-and-push and test-and-lint) include a `test` job that runs `python3 -m pytest tests/ -v --tb=short -x` with appropriate environment variables (`DATABASE_URL`, `API_KEY`, `JWT_SECRET`, `APP_ENV`). The build jobs depend on the test job passing first via `needs: test`. 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 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#1435
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?