Repository navigation
ci: run tests on GitHub Actions - #1
Merged
Merged
Conversation
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
1 participant
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.
Adds a GitHub Actions workflow (push to main + pull requests): Node 20 with npm cache,
npm ci,npm run prisma:generate,npm run build(typechecks and builds shared, server and client), thennpm test(server Jest suite).The server tests mock the Prisma client via jest-mock-extended, so no Postgres service is required. The
lintscript is not run because the repo has no ESLint config (eslint is not a dependency), so it currently fails everywhere.Also adds a CI status badge under the README title.
Local run: 7 suites, 35 tests passed; all three workspaces build.