Minor bugs in integration-tests

Open
#1,363 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the integration tests named in the issue: InfoTest, v3.OrganizationsTest.getDefaultDomain, and the serviceInstances package. Check the referenced pull request 1364 before making changes; done means the tests handle disabled v2 API and kind-deployment landscapes, and the package name matches its class declaration.

Written by the indexing model from the issue text.

Description

The "InfoTest" fails if running against a CF where v2 API is disabled.
.v3.OrganizationsTest.getDefaultDomain fails when running in kind-deployment landscape.

The package "serviceInstances" (with capital "I") does not match the package declaration in the contained class. This creates problems in Eclipse on Windows.

Pull request will follow.
https://github.com/cloudfoundry/cf-java-client/pull/1364

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.