-
Notifications
You must be signed in to change notification settings - Fork 683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GEODE-3530: refactor ListClientCommandDUnitTest #2129
Conversation
Co-authored-by: Jinmei Liao <jiliao@pivotal.io>
Co-authored-by: Jinmei Liao <jiliao@pivotal.io>
locator = cluster.startLocatorVM(0); | ||
int locatorPort = locator.getPort(); | ||
server1 = cluster.startServerVM(1, | ||
r -> r.withRegion(RegionShortcut.REPLICATE, "stocks").withConnectionToLocator(locatorPort)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"stocks" could be extracted into a final String local variable since it is used throughout these tests. Makes it easier to change the name of the region down the line if we need to (one place to change)
int server2port = server2.getPort(); | ||
Properties client1props = new Properties(); | ||
client1props.setProperty("name", "client-1"); | ||
client1 = cluster.startClientVM(3, client1props, cf -> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a fan of extracting ID numbers like 3
here into a local variable i.e. client1ID, so when we use it later its obvious what we are working with next time we use it (shutting down the client).
geode-cq/src/test/java/org/apache/geode/management/internal/cli/commands/ListClientCommandDUnitTest.java
Precheckin fails for |
Co-authored-by: Jinmei Liao <jiliao@pivotal.io>
Co-authored-by: Jinmei Liao jiliao@pivotal.io
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
Has your PR been rebased against the latest commit within the target branch (typically
develop
)?Is your initial contribution a single, squashed commit?
Does
gradlew build
run cleanly?Have you written or updated unit tests to verify your changes?
If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.