Test coverage: gate + nightly live tests for devnet/mainnet/mesa (#181)#199
Open
dkijania wants to merge 1 commit into
Open
Test coverage: gate + nightly live tests for devnet/mainnet/mesa (#181)#199dkijania wants to merge 1 commit into
dkijania wants to merge 1 commit into
Conversation
…mesa Two gaps from the test-coverage audit (#181): no coverage threshold in CI, and no live integration tests against real per-network data (devnet existed only as a static dump; mainnet was one skipped endpoint; mesa had none). - Add a coverage gate to `test:coverage` via c8 `--check-coverage` (lines 50, functions 50, statements 50, branches 80). Current coverage (~53% lines, 95% branches) clears it; the floor blocks regressions and rises as the suite grows. - Add a `test:live-api` script that runs the live-api suite against `STAGING_GRAPHQL_ENDPOINT`. - Add the `Live Integration` workflow: nightly + manual, runs the live-api suite against devnet/mainnet/mesa using per-network repo variables (`*_ARCHIVE_API_URL`), skipping any network without a configured endpoint so it stays green until they're set. `fail-fast: false` keeps networks independent. - Document the setup and the remaining `actions`/successful-`zkappCommands` fixture work in the live-api README. Closes #181. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QSuak9smCHbp4N17xjjLF6
dkijania
added
enhancement
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.
What & why
Part of the production-readiness epic (#163). Closes #181.
Two gaps from the test-coverage audit: no coverage threshold in CI, and no live integration tests against real per-network data (devnet existed only as a static dump; mainnet was a single skipped endpoint; mesa had none).
Changes
test:coveragenow runs c8 with--check-coverage --lines 50 --functions 50 --statements 50 --branches 80. Current coverage (~53% lines, 95% branches) clears it; the floor blocks regressions and can be raised as the suite grows (this epic adds ~10 test files).test:live-apiscript — runs the live-api suite againstSTAGING_GRAPHQL_ENDPOINT.Live Integrationworkflow — nightly + manual; runs live-api against devnet/mainnet/mesa using per-network repo variables (DEVNET_/MAINNET_/MESA_ARCHIVE_API_URL). A network with no configured endpoint is skipped, so the job is green until the maintainer sets the URLs;fail-fast: falsekeeps networks independent.Honest remaining work (documented, not silently skipped)
*_ARCHIVE_API_URLrepo variables for the nightly runs to actually exercise each network.actions.test.tsis still a placeholder and a successful-zkappCommandsfixture is still needed — both require known mainnet/mesa zkApps to snapshot against. Noted in the README.Testing
npm run test:coverage→ passes the gate locally (exit 0)npm run lint/npx prettier --debug-check .— clean🤖 Generated with Claude Code