cloudfoundry / cloudfoundry/cf-java-client
Integration tests depend on optional "routing" endpoint
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 334
- Forks
- 319
- PR merge metrics
- No merged PRs in 30d
Description
When running the integration tests of cf-java-client, some of them fail because they depend on the routing-api. The routing-api is optional and by default not installed.
The tests should be aware of the installation state (it is reported by a "null" value when calling the "/" endpoint. They should be skipped when the routing-api is not installed.
I will push some corrections.
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 the cf-java-client integration tests that call the routing-api and inspect the "/" endpoint response for the routing installation state. Make those tests skip when the response reports a null routing value, while retaining their checks when routing-api is installed. Run the integration test suite in environments with and without the optional endpoint to verify both paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100