Repository navigation
Conversation
Member
Author
|
Closing in favour of a tests-first stack: one PR that locks current behaviour with tests only (no source changes), then a separate PR with the source changes, then CI. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Third of three stacked PRs (server → client packages → CI).
What
Adds
.github/workflows/test.yml, the repo's first CI. On every PR and on pushes tomain, three jobs run in parallel, each with a Postgres service container:@superinterface/react(the server imports its build), then runs the full server suite under supercov..github/scripts/checkCoverage.mjsfails a job when its tests fail, its supercov run isn't valid, or coverage drops below the floor:Secrets
Real-provider integration tests read
TEST_OPENAI_API_KEY,TEST_ANTHROPIC_API_KEY,TEST_GOOGLE_API_KEY,TEST_OPENROUTER_API_KEYand theTEST_AZURE_*values (same names aspackages/server/.env.test). Without them those tests skip with a reason and CI stays green; Docker computer-use tests skip in CI because thecomputer-use-mcprepo isn't checked out.Verified
All three jobs' steps pass locally in a clean checkout without
.envfiles or provider keys. This PR's own run is the first on GitHub.