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 that gates the image build #1084

New Issue
Closed
opened 2026-03-29 20:24:33 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 20:24:33 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap reference: P2 / CI/CD - missing test stage

The build.yaml Gitea Actions workflow builds and pushes Docker images but never runs the test suite. Broken code can be shipped as long as it builds.

What to do

  • Add a test job to build.yaml (or a separate test.yaml workflow) that:
    • Sets up Python and installs dependencies.
    • Starts a test PostgreSQL service container.
    • Runs pytest tests/ with coverage output.
  • Make the build job depend on test so images are only pushed when tests pass.

Acceptance criteria

  • pytest runs on every push and pull request.
  • A failing test blocks the image build/push step.
  • CI passes on the current codebase with the existing test suite.
## Context Roadmap reference: P2 / CI/CD - missing test stage The `build.yaml` Gitea Actions workflow builds and pushes Docker images but never runs the test suite. Broken code can be shipped as long as it builds. ## What to do - Add a `test` job to `build.yaml` (or a separate `test.yaml` workflow) that: - Sets up Python and installs dependencies. - Starts a test PostgreSQL service container. - Runs `pytest tests/` with coverage output. - Make the `build` job depend on `test` so images are only pushed when tests pass. ## Acceptance criteria - [ ] `pytest` runs on every push and pull request. - [ ] A failing test blocks the image build/push step. - [ ] CI passes on the current codebase with the existing test suite.
AI-Manager added the P2agent-readysmalltestci labels 2026-03-29 20:24:33 +00:00
AI-Manager commented 2026-03-29 21:04:07 +00:00
Author
Owner
Copy Link
Copy Source

Resolved by PR #32 (commit fbb72fe) which added pytest and ruff linting to the CI workflow. Closing as complete.

Resolved by PR #32 (commit fbb72fe) which added pytest and ruff linting to the CI workflow. Closing as complete.
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 test
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#1084
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?