geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Rhomberg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-4052) Expand GfshExitCodeStatusCommandTest into multiple classes for more meaningful failure reporting
Date Tue, 05 Dec 2017 18:58:00 GMT

     [ https://issues.apache.org/jira/browse/GEODE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Patrick Rhomberg updated GEODE-4052:
------------------------------------
    Description: 
Occasionally, the majority of this class's tests will fail due to being unable to start the
cluster.  Such a failure is beyond the scope of the test and should be reported quickly.

This class should be divided into two classes, one containing those tests that require the
cluster's server to be running and one that does not.  The cluster start-up in both cases
should be delegated to a {{@BeforeClass}} method so that failure occurs as the class level
and is quickly recognizable.

  was:
Occasionally, the majority of this class's tests will fail due to being unable to start the
cluster.  Such a failure is beyond the scope of the test and should be reported quickly.

This class should be divided into two classes, one containing those tests that require the
cluster to be running and one that does not.  The cluster start-up should then be delegated
to a {{@BeforeClass}} method so that failure occurs as the class level and is quickly recognizable.


> Expand GfshExitCodeStatusCommandTest into multiple classes for more meaningful failure
reporting
> ------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-4052
>                 URL: https://issues.apache.org/jira/browse/GEODE-4052
>             Project: Geode
>          Issue Type: Test
>          Components: gfsh, tests
>            Reporter: Patrick Rhomberg
>            Assignee: Patrick Rhomberg
>
> Occasionally, the majority of this class's tests will fail due to being unable to start
the cluster.  Such a failure is beyond the scope of the test and should be reported quickly.
> This class should be divided into two classes, one containing those tests that require
the cluster's server to be running and one that does not.  The cluster start-up in both cases
should be delegated to a {{@BeforeClass}} method so that failure occurs as the class level
and is quickly recognizable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message