Skip to content

test: add backend safety regression suite and CI - #3

Merged
harshitethic merged 2 commits into
mainfrom
test/backend-ci-safety
Sep 7, 2026
Merged

test: add backend safety regression suite and CI#3
harshitethic merged 2 commits into
mainfrom
test/backend-ci-safety

Conversation

@harshitethic

Copy link
Copy Markdown
Owner

Problem

PatchPilot's backend currently has no automated regression suite or GitHub Actions workflow, so core safety helpers and request validation can regress without a visible CI signal.

What this adds

  • regression tests for repository/branch name normalization
  • structured JSON parsing coverage
  • exact edit application behavior
  • repository path-escape rejection
  • atomic edit behavior when a later edit is invalid
  • required GitHub token handling
  • RunRequest iteration validation
  • health contract coverage
  • GitHub Actions CI on Python 3.11 and 3.12
  • source compilation before the test suite
  • least-privilege contents: read workflow permissions

Validation

I could not execute the suite locally in the current automation environment because outbound GitHub resolution is blocked, so no local test result is claimed. This PR intentionally adds GitHub Actions as the authoritative validation path; CI should run python -m compileall app tests and python -m unittest discover -s tests -v for both supported Python versions.

Scope

This is deliberately limited to backend regression coverage and CI. It does not change runtime behavior or add product features.

@harshitethic
harshitethic merged commit e0298e5 into main Sep 7, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant