Integration tests depend on optional "routing" endpoint

Open
#1,249 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
api, testing

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.

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.

Dominant language
Java
Stars
334
Forks
319
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudfoundry/cf-java-client

All issues in cloudfoundry/cf-java-client

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.