Cause a TestNG test to fail?

Question

Is assert(false); an acceptable way to cause a test to fail?

Also, should I even be causing a TestNG test to fail if a NoSuchMethodException or SecurityException is thrown while trying to access private methods of a class or should I just print the exception's stack trace?

@Test
public void getLevelTest() {
    try {
        menu.getClass().getDeclaredMethod("getLevel",int.class,String.class);
    } catch (NoSuchMethodException | SecurityException e) {
        assert(false);
    }
}

score 3 · Answer 1 · edited Aug 03 '17 at 11:05

3

Another way to handle expected exceptions in the TestNG framework is:

@Test(expectedExceptions = {NoSuchMethodException.class, SecurityException.class})

If the test annotated with this encounters any of the exceptions, it will be considered a pass.

edited Aug 03 '17 at 11:05

Adowrath

701
11
24

answered Jun 28 '13 at 18:29

Marco Corona

812
6
12

Nathan Hughes · Accepted Answer · 2013-06-28T18:41:09.440

In this case using assert(false) means you lose the information about what exception was thrown. TestNG doesn't know that the exception had anything to do with the test failure.

You shouldn't need to assert anything or catch anything:

@Test
public void getLevelTest() throws Exception {
        menu.getClass().getDeclaredMethod("getLevel",int.class,String.class);
}

The test framework will capture the exception and print the stack trace in the test results.

score 2 · Answer 3 · edited May 23 '17 at 12:21

2

Use assertTrue() and assertFalse(), also see old answer on this topis.

edited May 23 '17 at 12:21

Community

1
1

answered Jun 28 '13 at 18:30

Cause a TestNG test to fail?

3 Answers3