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

New Issue
Closed
opened 2026-03-28 12:23:41 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 12:23:41 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P2 CI/CD — Test Stage

build.yaml in the Gitea Actions workflow builds and pushes container images but never runs pytest. Test failures are not caught in CI, allowing broken code to be packaged.

What to do

  • Add a test job to .gitea/workflows/build.yaml (or equivalent)
  • The test job should: install Python dependencies, run pytest tests/ and fail the workflow if any test fails
  • Configure the build job to depend on the test job (needs: test) so images are only built when tests pass
  • Ensure the test job has access to any required environment variables (use dummy/test values for secrets)

Acceptance criteria

  • A failing test causes the CI workflow to fail before the build/push step
  • A passing test suite allows the build to proceed
  • The test job runs on every push and pull request
## Context Roadmap item: P2 CI/CD — Test Stage `build.yaml` in the Gitea Actions workflow builds and pushes container images but never runs `pytest`. Test failures are not caught in CI, allowing broken code to be packaged. ## What to do - Add a `test` job to `.gitea/workflows/build.yaml` (or equivalent) - The test job should: install Python dependencies, run `pytest tests/` and fail the workflow if any test fails - Configure the `build` job to depend on the `test` job (`needs: test`) so images are only built when tests pass - Ensure the test job has access to any required environment variables (use dummy/test values for secrets) ## Acceptance criteria - A failing test causes the CI workflow to fail before the build/push step - A passing test suite allows the build to proceed - The test job runs on every push and pull request
AI-Manager added the P2agent-readysmall labels 2026-03-28 12:23:41 +00:00
AI-Manager commented 2026-03-28 13:03:32 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. The CI workflow (.gitea/workflows/) includes a Run pytest step that executes python3 -m pytest tests/ -v --tb=short -x with appropriate environment variables.

Closing as already implemented. The CI workflow (`.gitea/workflows/`) includes a `Run pytest` step that executes `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 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#651
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?