Allow selecting `AuthScheme` in integration tests
- Dominant language
- Rust
- Stars
- 78
- Forks
- 129
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 52
Description
The integration-tests binary (bin/integration-tests) hardcodes `RPO_FALCON_SCHEME_ID` (`AuthSchemeId::Falcon512Poseidon2`) in ~40+ wallets and faucets across tests. The helpers already accept an `AuthSchemeId`, and the client supports `EcdsaK256Keccak` too, but there's no way to exercise it from the integration suite.
We could add an --auth-scheme CLI flag to and carry it through `ClientConfig`.
Contributor guide
Research direction
Start by examining the integration-tests binary (bin/integration-tests) to see how AuthSchemeId is currently hardcoded. Look at the helpers that already accept an AuthSchemeId and the client support for EcdsaK256Keccak. Add an --auth-scheme CLI flag and propagate it through ClientConfig. Test by running the integration suite with the new flag to ensure both auth schemes work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100