Skip to content

Split backend unit and integration test suites#639

Open
nensii21 wants to merge 1 commit into
utksh1:mainfrom
nensii21:fix/backend-ci-split-tests
Open

Split backend unit and integration test suites#639
nensii21 wants to merge 1 commit into
utksh1:mainfrom
nensii21:fix/backend-ci-split-tests

Conversation

@nensii21
Copy link
Copy Markdown

@nensii21 nensii21 commented Jun 6, 2026

Summary

  • Split backend test execution into separate unit and integration jobs
  • Preserved benchmark exclusion with -m "not benchmark"
  • Improved CI failure visibility by reporting unit and integration failures independently

Validation

  • Unit test suite runs independently
  • Integration test suite runs independently
  • Benchmark exclusion behavior unchanged

@nensii21
Copy link
Copy Markdown
Author

nensii21 commented Jun 6, 2026

The workflow has been updated to split backend testing into separate unit and integration jobs.

Current CI failures appear unrelated to this change:

  • backend-lint fails due to an existing Ruff error (F821 Undefined name 'db' in backend/secuscan/workflows.py)
  • frontend-checks fails in an existing frontend test (testing/unit/pages/Workflows.test.tsx)

The new backend-unit-tests and backend-integration-tests jobs are present in the workflow but are skipped because they depend on backend-lint succeeding.

GitHub is also still expecting the legacy backend-tests status check, which appears to come from branch protection settings.

@nensii21 nensii21 force-pushed the fix/backend-ci-split-tests branch from 2a4869a to c7af3ff Compare June 6, 2026 16:08
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