mozilla / mozilla/authenticator-rs
Rewrite tests that use mock devices
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 316
- Forks
- 82
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 1
Description
The mock device tests (e.g. test_get_assertion_ctap2_pre_flight) are hard to maintain because they simultaneously test high-level protocol behavior and low-level serialization details. We should have separate tests for protocol behavior and serialization. The protocol behavior tests should use virtual authenticators.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with test_get_assertion_ctap2_pre_flight in src/ctap2/commands/get_assertion.rs and review how the mock device is used. Identify the existing virtual authenticator test entry points and separate protocol-behavior coverage from low-level serialization coverage. Done means the protocol tests use virtual authenticators and serialization is tested independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100