Update proving flow tests for new UI and add ProvingScreenRouter tests #1559
+326
−64
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
DocumentSelectorForProvingScreenand remove assertions that no longer match the updated components.ProvingScreenRouterso skip/auto-select behavior and retry handling are validated.@selfxyz/mobile-sdk-alphahelpers (isDocumentValidForProving,getDocumentAttributes,useSelfClient) used by the new implementation.Description
app/tests/src/screens/verification/DocumentSelectorForProvingScreen.test.tsxto mock@selfxyz/mobile-sdk-alphafunctions, adapt testIDs to the redesigned proof request card, and add tests covering disclosure items and the wallet badge/modal while removing outdated cases.app/tests/src/screens/verification/ProvingScreenRouter.test.tsxthat covers routing toDocumentDataNotFound, auto-select+route toProve, routing toDocumentSelectorForProving, and retry flow on load failure.Testing
yarn workspace @selfxyz/mobile-app testor the repo-wide test suite withyarn test.yarn installand test memory guidelines fromAGENTS.mdare followed before running tests to avoid CI OOM failures.Codex Task