Is it good to use the JUnit test method in the test class?

Question

Consider a Java class with small static library-style methods.

Is it wrong to use JUnit testing methods in one class?

I see the following pros:

• JUnit test as stand-alone documentation is next to the method code
• It will be easy to move this code to another class or package.

What are contrasts and why is it a common practice to always separate test code?

Example:

import org.junit.*;

public class HtmlUtils {
    public static String normalizeBrs(String html) {
        return html.replaceAll("<br\\s*/?>", "<br/>");
    }

    @Test
    public void testNormalizeBrs() {
        Assert.assertEquals(normalizeBrs("hello <br /> world <br>"), "hello <br/> world <br/>");
    }
}

Answer 1

(Is it wrong to apply the JUnit test method to the test class?)

Absolutely .

: . , , / .

- " ".

: - - -. .

, ... - .

- "", , , .

, .

- x.y.Z... x.y.ZTest; , , .

: Java " " 2017 . , () . ( , , , : )

, , , , . , . API ; .

Answer 2

, .

, , 1000 , 10 . 10 .

, + ?

- , , - .

. , .

Answer 3

.

, .

• . .
• . , , . , , .
• - , . .

.

!!!

Answer 4

,

, , test, . . , , , .

http://www.javaworld.com/article/2076265/testing-debugging/junit-best-practices.html http://www.kyleblaney.com/junit-best-practices/

Answer 5

, :

• (, , jar/war/ear, , ) (, Mockito,...),
• , , , .
• , api ( , ).
• , . of maven

Answer 6

- , Maven .

src/main src/test, .

src/main .

src/test .

.

. , jUnit . , (JMock, Mockito), , Hamcrest, , WireMock RestClientDriver, ..

, , .

, . , .

Maven , . , jUnit, Mockito .. , - , .

:

• .
• , ,

, Java-, , . .

:

• " JUnit "

, . , , , , . , C #IFDEF TEST. , "" -, , , !

Maven Java-, , . IDE ( ) unit test - .

• " "

, IDE ( ) . , , IntelliJ IDEA, , - , .

-

, , Maven, Gradle - .