Uh oh!
There was an error while loading. Please reload this page.
HBASE-22382 Refactor tests in TestFromClientSide - #385
Conversation
anmolnar
commented
Jul 16, 2019
retest build |
Apache-HBase
commented
Jul 16, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 17, 2019
🎊 +1 overall
This message was automatically generated. |
| public void testNull() throws Exception { | ||
| final TableName tableName = TableName.valueOf(name.getMethodName()); | ||
| public void testNull_TableName() { |
There was a problem hiding this comment.
testNullTableName? I thought we should keep use Camel-Case for method name.
| } | ||
| @Test | ||
| public void testNull_FamilyName() { |
There was a problem hiding this comment.
Ditto. Please update other methods' name too. Thanks.
Apache-HBase
commented
Jul 21, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 22, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 22, 2019
💔 -1 overall
This message was automatically generated. |
| try { | ||
| TEST_UTIL.createTable((TableName)null, FAMILY); | ||
| fail("Creating a table with null name passed, should have failed"); | ||
| } catch(Exception e) {} |
There was a problem hiding this comment.
Since we have split the method, we can use the @test(expected = XXXException.class) so we do not need to catch the exception any more?
There was a problem hiding this comment.
Right. Makes perfect sense.
| @@ -1234,7 +1246,14 @@ public void testNull() throws Exception { | |||
| } catch (Exception e) { | |||
| throw new IOException("Using a row with null qualifier threw exception, should "); | |||
There was a problem hiding this comment.
Not your fault but since this is a refactoring, let's fix the message?
| } | ||
| @Test | ||
| @SuppressWarnings("checkstyle:MethodLength") |
There was a problem hiding this comment.
Maybe in the future we will also split these methods so let's do not suppress the warning?
There was a problem hiding this comment.
I tried to do so. But it seems to me that these tests are doing a sequence of operations which cannot be broken without doing a lot of redundant initialisation logic. I believe that the gain of making these tests smaller doesn't overcome the hit on the efficiency.
To be honest, checkstyle rule for maximizing the size of integration tests doesn't make sense to me.
| } | ||
| @Test | ||
| @SuppressWarnings("checkstyle:MethodLength") |
Apache-HBase
commented
Jul 23, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 23, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 23, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 23, 2019
🎊 +1 overall
This message was automatically generated. |
anmolnar
commented
Jul 23, 2019
@Apache9 It's done and the build is green again. PTAL. |
Apache9
commented
Jul 23, 2019
My comments are still not resolved? |
anmolnar
commented
Jul 23, 2019
…ption, fixed language
Apache-HBase
commented
Jul 23, 2019
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 24, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 24, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 24, 2019
💔 -1 overall
This message was automatically generated. |
Signed-off-by: Duo Zhang <zhangduo@apache.org>
Signed-off-by: Duo Zhang <zhangduo@apache.org>
Signed-off-by: Duo Zhang <zhangduo@apache.org>
Signed-off-by: Duo Zhang <zhangduo@apache.org>
Signed-off-by: Duo Zhang <zhangduo@apache.org> (cherry picked from commit dcc2c4d) Change-Id: I771e7713240700a47a55fdb743efc1e184c51856
testNull()into multiple,testVersionLimits()- cannot split,testDeletesWithReverseScan()- cannot split