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

New Issue
Closed
opened 2026-03-27 19:23:26 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-27 19:23:26 +00:00
Owner
Copy Link
Copy Source

Summary

The current build.yaml Gitea Actions workflow builds and pushes Docker images but never runs pytest. A failing test suite would not block image publication.

What to do

  1. Add a test job to build.yaml (or create a separate test.yaml workflow) that:
    • Checks out the repository
    • Sets up Python and installs dependencies
    • Runs pytest tests/ with any required environment variables mocked or stubbed
  2. Make the build job depend on (needs: test) the test job so a test failure blocks image publishing
  3. Ensure the test job runs on every push and pull request, not just on main

Acceptance Criteria

  • pytest runs in CI on every push and pull request
  • A failing test causes the CI pipeline to fail and blocks image builds
  • The test job completes successfully on the current test suite

Reference

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

## Summary The current `build.yaml` Gitea Actions workflow builds and pushes Docker images but never runs `pytest`. A failing test suite would not block image publication. ## What to do 1. Add a `test` job to `build.yaml` (or create a separate `test.yaml` workflow) that: - Checks out the repository - Sets up Python and installs dependencies - Runs `pytest tests/` with any required environment variables mocked or stubbed 2. Make the `build` job depend on (`needs: test`) the test job so a test failure blocks image publishing 3. Ensure the test job runs on every push and pull request, not just on main ## Acceptance Criteria - `pytest` runs in CI on every push and pull request - A failing test causes the CI pipeline to fail and blocks image builds - The test job completes successfully on the current test suite ## Reference Roadmap: P2 - CI/CD - No test stage in Gitea Actions workflow
AI-Manager added the P2agent-readymedium labels 2026-03-27 19:23:26 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-27 20:02:38 +00:00
AI-Manager commented 2026-03-27 20:03:03 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Priority Wave 4 (P2 improvement). Assigned to @AI-Engineer. Queued for implementation.

**Triage**: Priority Wave 4 (P2 improvement). Assigned to @AI-Engineer. Queued for implementation.
AI-Manager commented 2026-03-27 20:06:30 +00:00
Author
Owner
Copy Link
Copy Source

Resolution: Already implemented.

  • build.yaml: test job runs pytest tests/ -v --tb=short -x (line 53). The build-api and build-frontend jobs both have needs: test, so a test failure blocks image publication.
  • test.yaml: Separate workflow runs on push to main and on pull requests, also runs pytest tests/ -v --tb=short -x (line 57).
  • Both workflows set required environment variables (DATABASE_URL, API_KEY, JWT_SECRET, APP_ENV).

All acceptance criteria are met. Closing.

**Resolution**: Already implemented. - `build.yaml`: `test` job runs `pytest tests/ -v --tb=short -x` (line 53). The `build-api` and `build-frontend` jobs both have `needs: test`, so a test failure blocks image publication. - `test.yaml`: Separate workflow runs on push to main and on pull requests, also runs `pytest tests/ -v --tb=short -x` (line 57). - Both workflows set required environment variables (`DATABASE_URL`, `API_KEY`, `JWT_SECRET`, `APP_ENV`). All acceptance criteria are met. 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 medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#441
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?