I ran across some state code that had plugs in it that were operations an action\u00a0listener would look for. \u00a0The code methods didn’t\u00a0have anything in them, but needed to be there. \u00a0I wanted some simple unit testing coverage on them. \u00a0Here’s a small technique to cover a void method that doesn’t do too much.<\/p>\n
Here’s the code to be tested. Notice I made 2 methods for my tests, one throws an error. I’ve included to ways of testing for errors in the attached repository code.<\/p>\n
\r\npublic class TestClassImpl implements TestClass {\r\n public void methodNoError() {}\r\n public void methodError() {throw new RuntimeException();}\t\r\n}\r\n<\/code><\/pre>\n <\/p>\n
To test methodNoError, we just use a Boolean and flag it if there is an error, and assert that variable. The other two tets are separate ways to check methodError() which actually throws an error.<\/p>\n
\r\n@Test\r\npublic void testMethodNoError() {\t\r\n Boolean testState = true;\t\r\n try {\t\r\n testClass.methodNoError();\t\r\n } catch (Exception e) {\r\n testState = false;\r\n }\t\t\r\n assertTrue(testState);\r\n}\r\n\t\r\n@Test\r\npublic void testMethodError() {\t\r\n Boolean testState = true;\r\n try {\t\r\n testClass.methodError();\t\r\n } catch (Exception e) {\r\n testState = false;\r\n }\t\r\n assertFalse(testState);\r\n}\r\n\t\r\n@Test(expected = Exception.class)\r\npublic void testMethodErrorExpected() {testClass.methodError();}\r\n<\/code><\/pre>\n <\/p>\n
You can try this out with the TestVoid project folder in my Bitbucket; just run “mvn clean install” or load it into your IDE.<\/p>\n