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 build workflow #1607

New Issue
Closed
opened 2026-04-19 23:25:16 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-04-19 23:25:16 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P2 - CI/CD

The build.yaml workflow builds and pushes Docker images but never runs pytest. Test failures can therefore ship undetected.

What to do

  • Add a test job to build.yaml that runs before the build job
  • The test job should: install Python dependencies, spin up a test database (or use mocks), and run pytest tests/
  • Make the build job depend on the test job (needs: test) so a test failure blocks the image push

Acceptance criteria

  • build.yaml contains a test job that runs pytest
  • The build/push job only runs if tests pass
  • CI fails visibly when a test is broken
  • README or CI badge reflects the test status

Ref: ROADMAP.md P2 - CI/CD

## Context Roadmap item: P2 - CI/CD The `build.yaml` workflow builds and pushes Docker images but never runs `pytest`. Test failures can therefore ship undetected. ## What to do - Add a `test` job to `build.yaml` that runs before the build job - The test job should: install Python dependencies, spin up a test database (or use mocks), and run `pytest tests/` - Make the build job depend on the test job (`needs: test`) so a test failure blocks the image push ## Acceptance criteria - [ ] `build.yaml` contains a `test` job that runs `pytest` - [ ] The build/push job only runs if tests pass - [ ] CI fails visibly when a test is broken - [ ] README or CI badge reflects the test status Ref: ROADMAP.md P2 - CI/CD
AI-Manager added the P2agent-readysmallci labels 2026-04-19 23:25:16 +00:00
AI-Manager commented 2026-04-20 04:08:35 +00:00
Author
Owner
Copy Link
Copy Source

This issue is already resolved in main. Both build.yaml and test.yaml CI workflows include a pytest stage that runs python3 -m pytest tests/ -v --tb=short -x with appropriate environment variables.

This issue is already resolved in main. Both `build.yaml` and `test.yaml` CI workflows include a pytest stage that runs `python3 -m pytest tests/ -v --tb=short -x` with appropriate environment variables.
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#1607
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?