LukeMathWalker / LukeMathWalker/wiremock-rs
Poor UX for large bodies (or bodies with binary data).
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 799
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
The entire request being printed out when the body is exceptional large or contains binary data leads to poor debugging when a guard fails. I could provide a real example from one of our tests but it's >10MB of binary data so I'll leave that to the imagination instead :sweat_smile:
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
The issue names no file or test. Start by locating where failed guards format and print the full request body, then reproduce the problem with an oversized or binary body. Done means failure output remains useful without dumping the entire request, with regression coverage for the reported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100