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

New Issue
Closed
opened 2026-03-30 04:24:26 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 04:24:26 +00:00
Owner
Copy Link
Copy Source

Context

build.yaml in Gitea Actions builds and pushes Docker images but never runs the test suite. A broken test can be merged and shipped without anyone noticing.

Roadmap reference: ROADMAP.md > P2 > CI/CD > No test stage in the Gitea Actions workflow

What to do

  1. Add a test job to .gitea/workflows/build.yaml (or create a separate test.yaml).
  2. The job should:
    • Check out the code.
    • Start a PostgreSQL service container for integration tests.
    • Install Python dependencies.
    • Run pytest with coverage reporting.
  3. Make the build (image push) job depend on the test job passing.

Acceptance criteria

  • A failing test causes the CI pipeline to fail before images are pushed.
  • pytest output (pass/fail summary) is visible in the CI logs.
  • The workflow runs on every push to main and on all pull requests.
## Context `build.yaml` in Gitea Actions builds and pushes Docker images but never runs the test suite. A broken test can be merged and shipped without anyone noticing. Roadmap reference: ROADMAP.md > P2 > CI/CD > No test stage in the Gitea Actions workflow ## What to do 1. Add a `test` job to `.gitea/workflows/build.yaml` (or create a separate `test.yaml`). 2. The job should: - Check out the code. - Start a PostgreSQL service container for integration tests. - Install Python dependencies. - Run `pytest` with coverage reporting. 3. Make the `build` (image push) job depend on the `test` job passing. ## Acceptance criteria - [ ] A failing test causes the CI pipeline to fail before images are pushed. - [ ] `pytest` output (pass/fail summary) is visible in the CI logs. - [ ] The workflow runs on every push to `main` and on all pull requests.
AI-Manager added the P2agent-readymediumci labels 2026-03-30 04:24:26 +00:00
AI-Manager commented 2026-03-30 05:04:58 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved on main. .gitea/workflows/test.yaml includes a pytest step (lines 58-67) that runs python3 -m pytest tests/ -v --tb=short -x with appropriate test environment variables. Closing as complete.

This issue has been resolved on main. `.gitea/workflows/test.yaml` includes a pytest step (lines 58-67) that runs `python3 -m pytest tests/ -v --tb=short -x` with appropriate test environment variables. 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 medium
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#1207
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?