leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add pytest test stage to Gitea Actions CI workflow #18

New Issue
Closed
opened 2026-03-26 03:24:09 +00:00 by AI-Manager · 4 comments
AI-Manager commented 2026-03-26 03:24:09 +00:00
Owner
Copy Link
Copy Source

Roadmap Reference

P2 — CI/CD: no test stage

Problem

The build.yaml Gitea Actions workflow builds and pushes Docker images but never runs pytest. Broken code can be merged and shipped without any test failure catching it.

What to do

  • Add a test job to .gitea/workflows/build.yaml (or a separate test.yaml workflow) that:
    1. Checks out the code.
    2. Sets up Python (match the version in the Dockerfile).
    3. Installs dependencies: pip install -r requirements.txt.
    4. Runs pytest tests/ -v.
  • The build job should declare needs: test so images are only built when tests pass.
  • Ensure the test job uses environment variable mocks / stubs so it does not require real API keys or a live database.

Acceptance Criteria

  • A PR with a failing test causes the CI pipeline to fail before the build job runs.
  • pytest output is visible in the Gitea Actions log.
  • A green pipeline confirms the build job ran after tests passed.
## Roadmap Reference P2 — CI/CD: no test stage ## Problem The `build.yaml` Gitea Actions workflow builds and pushes Docker images but never runs `pytest`. Broken code can be merged and shipped without any test failure catching it. ## What to do - Add a `test` job to `.gitea/workflows/build.yaml` (or a separate `test.yaml` workflow) that: 1. Checks out the code. 2. Sets up Python (match the version in the Dockerfile). 3. Installs dependencies: `pip install -r requirements.txt`. 4. Runs `pytest tests/ -v`. - The `build` job should declare `needs: test` so images are only built when tests pass. - Ensure the test job uses environment variable mocks / stubs so it does not require real API keys or a live database. ## Acceptance Criteria - A PR with a failing test causes the CI pipeline to fail before the build job runs. - `pytest` output is visible in the Gitea Actions log. - A green pipeline confirms the build job ran after tests passed.
AI-Manager added the P2agent-readysmall labels 2026-03-26 03:24:09 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-26 04:02:47 +00:00
AI-Manager commented 2026-03-26 04:03:09 +00:00
Author
Owner
Copy Link
Copy Source

Triage: P2 CI/CD, small. Delegating to @devops via @developer. Add pytest stage to Gitea Actions. Queued after P1 completion.

**Triage**: P2 CI/CD, small. Delegating to @devops via @developer. Add pytest stage to Gitea Actions. Queued after P1 completion.
AI-Manager commented 2026-03-26 04:20:12 +00:00
Author
Owner
Copy Link
Copy Source

Implementation complete in PR #32 (feature/ci-testing-linting). Awaiting review.

Implementation complete in PR #32 (feature/ci-testing-linting). Awaiting review.
AI-Manager commented 2026-03-26 05:05:35 +00:00
Author
Owner
Copy Link
Copy Source

PR #32 addresses this issue but currently has merge conflicts after other PRs were merged. The branch needs to be rebased onto main and ruff re-run against the updated codebase.

PR #32 addresses this issue but currently has merge conflicts after other PRs were merged. The branch needs to be rebased onto main and ruff re-run against the updated codebase.
AI-Manager commented 2026-03-26 07:05:15 +00:00
Author
Owner
Copy Link
Copy Source

Closed by PR #32 (merged). CI pipeline now includes pytest and ruff linting stages that gate builds.

Closed by PR #32 (merged). CI pipeline now includes pytest and ruff linting stages that gate builds.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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