test(frontend): cover backend exchange env gate#13157
Draft
cursor[bot] wants to merge 2 commits into
Draft
Conversation
Co-authored-by: Antonio Ventilii <AntonioVentilii@users.noreply.github.com>
Co-authored-by: Antonio Ventilii <AntonioVentilii@users.noreply.github.com>
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.
Motivation
Recent exchange-rate work restricted backend exchange mode to LOCAL/STAGING builds so BETA/PROD cannot be opted into backend pricing by a canister runtime flag. That build-time gate controls a broad pricing path, so a regression could accidentally route production users away from the full frontend provider path.
Risky behavior now covered:
BACKEND_EXCHANGE_ENABLEDis true for local and staging-shaped builds.BACKEND_EXCHANGE_ENABLEDis false for beta and production-shaped builds.Changes
src/frontend/src/tests/env/exchange.env.spec.ts.src/frontend/src/env/exchange.env.tsunder mocked app environment constants to assert the backend exchange environment matrix directly.These tests materially reduce regression risk by locking the build-time production/staging split without relying only on indirect service-level mocks.
Tests
PATH="$HOME/.nvm/versions/node/v24.17.0/bin:$PATH" npm run preparePATH="$HOME/.nvm/versions/node/v24.17.0/bin:$PATH" npm run test -- src/frontend/src/tests/env/exchange.env.spec.tsPATH="$HOME/.nvm/versions/node/v24.17.0/bin:$PATH" npm run format:file --file=src/frontend/src/tests/env/exchange.env.spec.tsPATH="$HOME/.nvm/versions/node/v24.17.0/bin:$PATH" npm run lint -- --max-warnings 0 src/frontend/src/tests/env/exchange.env.spec.tsPATH="$HOME/.nvm/versions/node/v24.17.0/bin:$PATH" npx eslint "src/frontend/src/tests/env/exchange.env.spec.ts" --max-warnings 0Note: dependencies were absent in the runner, so
npm ciwas run first with Node 24 fromnvm.