geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEODE-3872) Consolidate GfshShellConnectionRule assertions
Date Wed, 25 Oct 2017 22:28:00 GMT


ASF GitHub Bot commented on GEODE-3872:

jaredjstewart opened a new pull request #978: GEODE-3872: Consolidate GfshShellConnectionRule
   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:
   - [ x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
   - [ x] Has your PR been rebased against the latest commit within the target branch (typically
   - [x ] Is your initial contribution a single, squashed commit?
   - [x ] Does `gradlew build` run cleanly?
   - [ x] Have you written or updated unit tests to verify your changes?
   - [x ] 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

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Consolidate GfshShellConnectionRule assertions
> ----------------------------------------------
>                 Key: GEODE-3872
>                 URL:
>             Project: Geode
>          Issue Type: Improvement
>          Components: gfsh, tests
>            Reporter: Jared Stewart
>            Assignee: Jared Stewart
> We have started to accumulate several flavors of _executeCommand_ methods on GfshShellConnectionRule
that implicitly make certain kinds of assertions.  (For example, assertions on the command
result status or on the output text.)  It would make the code more maintainable to separate
the various assertion methods into a separate class and to have a single executeCommand method.
> (See e.g.

This message was sent by Atlassian JIRA

View raw message