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

New Issue
Closed
opened 2026-03-30 18:23:47 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 18:23:47 +00:00
Owner
Copy Link
Copy Source

Context

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

build.yaml builds and pushes Docker images but never runs the test suite. Broken code can be shipped to the registry without any automated validation.

What to do

  • Add a test job to build.yaml (or a separate test.yaml workflow) that:
    1. Sets up Python and installs dependencies (pip install -e .[dev] or pip install -r requirements-dev.txt).
    2. Runs pytest tests/ -v.
  • Make the build job depend on the test job so a failing test blocks the image push.
  • The test job should use a service container for PostgreSQL if the tests require it, or mock the DB connection.

Acceptance criteria

  • A pull request with a failing test causes CI to report failure before the image is built.
  • A pull request with passing tests proceeds to the build stage normally.
  • The workflow file is valid YAML and passes act or Giteas workflow linter.
## Context Roadmap item: P2 -- CI/CD -- No test stage in the Gitea Actions workflow `build.yaml` builds and pushes Docker images but never runs the test suite. Broken code can be shipped to the registry without any automated validation. ## What to do - Add a `test` job to `build.yaml` (or a separate `test.yaml` workflow) that: 1. Sets up Python and installs dependencies (`pip install -e .[dev]` or `pip install -r requirements-dev.txt`). 2. Runs `pytest tests/ -v`. - Make the `build` job depend on the `test` job so a failing test blocks the image push. - The test job should use a service container for PostgreSQL if the tests require it, or mock the DB connection. ## Acceptance criteria - [ ] A pull request with a failing test causes CI to report failure before the image is built. - [ ] A pull request with passing tests proceeds to the build stage normally. - [ ] The workflow file is valid YAML and passes `act` or Giteas workflow linter.
AI-Manager added the P2agent-readymediumci labels 2026-03-30 18:23:47 +00:00
AI-Manager commented 2026-03-30 19:05:36 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already resolved in main.

.gitea/workflows/test.yaml includes a pytest step (lines 58-67) that runs python3 -m pytest tests/ -v --tb=short -x with proper environment variables. The build workflow (build.yaml) also runs pytest as a gate before building images. Closing as complete.

**Triage: Already resolved in main.** `.gitea/workflows/test.yaml` includes a pytest step (lines 58-67) that runs `python3 -m pytest tests/ -v --tb=short -x` with proper environment variables. The build workflow (`build.yaml`) also runs pytest as a gate before building images. 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#1414
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?