Improve FrontendIntegrationTest
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
The coverage of `FrontendIntegrationTest` can be improved.
1. Add test cases for the "bad" scenarios (e.g. bad requests)
2. Add test cases for private blobs.
(more can be added)
Ideally, `FrontendIntegrationTest` in isolation should cover as much code as possible in ambry-rest and ambry-frontend (internal server errors probably cannot be tested since the frontend is expected to be treated like a black box).
Each of the enhancements can be converted into their own issues with more details. This one covers them at a high level.
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 FrontendIntegrationTest and inspect the ambry-rest and ambry-frontend paths it exercises. Identify untested bad-request scenarios and private-blob behavior, then add integration cases that verify those responses while treating the frontend as a black box. Done means the isolated test covers the agreed scenarios without relying on internal server errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100