TestSmell

Hi! We notice that the random number generator (RNG) is used to produce test code in your project. For example, a random generator in the test method named ''truncationTest() ''...

Test Smell: it is not a good practice to use the loop in the test

1

Hi! We notice that you use the loop structure in your test cases. For example, testInvalidChar() in NoiseCharactersTest.java However, using the loop in test cases is not a good test...

Test Smell: the wrong parameter order in ''assertEquals'' assertion

1

Hi! Description: we detect that some assertions in your test code have the wrong parameter orders. For example, the test case named ''copyFromContainerBinaryFile()'' in ''CopyArchiveFromContainerCmdIT.java'' writes the ''assertEquals'' assertion as...

Hi! We notice that you mix the production code and the corresponding test code into the same file. For example, In fact, it is a bad practice for code organization....

Hi! We notice that you mix the test code with the production code. For example, a test case in the ''neo4j-tutorial/blob/master/src/koan/java/org/neo4j/tutorial/Koan11.java'' path. In your project, ''.../src/...'' is the folder for...

Test Smell: it is not a good practice to write a return statement in the test case

5

Hi! I notice that you write a test case with a return statement. For example, It is not a good idea to write the return statement in your test case...

Test Smell: poor code organization

1

Hi! We notice that your way of naming test files doesn't follow the common naming convention. For example, a test file is named ''https://github.com/pentaho/pentaho-platform/blob/master/repository/src/it/java/com/pentaho/pdi/ws/RepositorySyncWebServiceIT.java'' The common convention (good practice) is...