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

New Issue
Closed
opened 2026-03-26 16:23:48 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-26 16:23:48 +00:00
Owner
Copy Link
Copy Source

Context

The current build.yaml workflow builds and pushes Docker images but never runs the test suite. Broken code can be shipped without any test gate.

Work

  • Add a test job to build.yaml that runs before the Docker build job.
  • The test job should: check out the code, set up Python, install dependencies, and run pytest.
  • Configure required environment variables for the test run (use dummy/test values for external services).
  • Make the Docker build job depend on the test job so a failing test blocks the image push.

Acceptance Criteria

  • Opening a PR or pushing to main triggers pytest in CI.
  • A failing test prevents the Docker image from being built and pushed.
  • CI passes on a clean main branch.

References

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

## Context The current build.yaml workflow builds and pushes Docker images but never runs the test suite. Broken code can be shipped without any test gate. ## Work - Add a test job to build.yaml that runs before the Docker build job. - The test job should: check out the code, set up Python, install dependencies, and run pytest. - Configure required environment variables for the test run (use dummy/test values for external services). - Make the Docker build job depend on the test job so a failing test blocks the image push. ## Acceptance Criteria - Opening a PR or pushing to main triggers pytest in CI. - A failing test prevents the Docker image from being built and pushed. - CI passes on a clean main branch. ## References Roadmap: P2 -- CI/CD -- No test stage in the Gitea Actions workflow.
AI-Manager added the P2agent-readysmall labels 2026-03-26 16:23:48 +00:00
AI-Manager commented 2026-03-26 17:03:25 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved. The CI workflow (.gitea/workflows/test.yml) includes a pytest test job that runs python3 -m pytest tests/ -v --tb=short -x with proper env vars.

Resolved by PR #32 ("ci: add pytest and ruff linting to CI workflow"). Closing.

This issue has already been resolved. The CI workflow (`.gitea/workflows/test.yml`) includes a pytest test job that runs `python3 -m pytest tests/ -v --tb=short -x` with proper env vars. Resolved by PR #32 ("ci: add pytest and ruff linting to CI workflow"). Closing.
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#129
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?