junit4

I have some tests like this: @Test public void test01() { Position p = getPositionAt('a', 1); assertNotNull("a1 exists", p); assertNotNull("figure exists a1", p.getFigure()); p = getPositionAt('a', 2); assertNotNull("exists a2", p); assertNull("figure exists a2", p.getFigure()); p = getPositionAt('b', 1); assertNotNull("exists b1", p); assertNull("figure exists b1", p.getFigure()); } What I need while running tests is to print each assert message to stdout and then result of the assert. This is require format from test class: a1 exists -success figure exists a1 -success exists a2 -success

I wrote a junit test to add two numbers. I need to pass this numbers from command line. I am running this junit test from maven tool as mvn -Dtest=AddNumbers My test program looks like this int num1 = 1; int num2 = 2; @Test public void addNos() { System.out.println((num1 + num2)); } How to pass these numbers from command line? Passing the numbers as system properties like suggested by @artbristol is a good idea, but I found that it is not always guaranteed that these properties will be propagated to the test. To be sure to pass the system properties to the test use the maven surefire plugin

I am having a problems running the following code: configService.setMainConfig("src/test/resources/MainConfig.xml"); From within a Junit @Before method. Is this the way Maven builds out its target folder? Tomasz Nurkiewicz Access MainConfig.xml directly. The src/test/resources directory contents are placed in the root of your CLASSPATH. More precisely: contents of src/test/resources are copied into target/test-classes , so if you have the following project structure: . └── src └── test ├── java │ └── foo │ └── C.java └── resources ├── a.xml └── foo └── b.xml It will result with the following

I'm trying to create the javadoc with maven and it fails. It also fails when doing the verify. mvn verify I get the following error: (...) [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /home/miquel/creaveu/createOmegaMatrix/src/main/java/edu/url/salle/gtm/hnm/dataStructures/HFrame.java:[6,23] package org.junit does not exist [ERROR] /home/miquel/creaveu/createOmegaMatrix/src/main/java/edu/url/salle/gtm/hnm/dataStructures/HFrame.java:[6,0] static import only from

What's the actual use of 'fail' in JUnit test case? Some cases where I have found it useful: mark a test that is incomplete, so it fails and warns you until you can finish it making sure an exception is thrown: try{ // do stuff... fail("Exception not thrown"); }catch(Exception e){ assertTrue(e.hasSomeFlag()); } Note: Since JUnit4, there is a more elegant way to test that an exception is being thrown: Use the annotation @Test(expected=IndexOutOfBoundsException.class) However, this won't work if you also want to inspect the exception, then you still need fail() . lets say you are writing a test

I'm pretty new to Java and am following the Eclipse Total Beginner's Tutorials . They are all very helpful, but in Lesson 12, he uses assertTrue for one test case and assertFalse for another. Here's the code: // Check the book out to p1 (Thomas) // Check to see that the book was successfully checked out to p1 (Thomas) assertTrue("Book did not check out correctly", ml.checkOut(b1, p1)); // If checkOut fails, display message assertEquals("Thomas", b1.getPerson().getName()); assertFalse("Book was already checked out", ml.checkOut(b1,p2)); // If checkOut fails, display message assertEquals("Book

public class SupportController{ public void disableUserAccount(String username) throws Exception { UserAccount userAccount = new UserAccount(Constants.SYSTEM, Constants.CONTAINER, username); UserAccount.disableAccount(); } } How would i test that the useraccount created is disabled? I would suggest using Mock Objects . Besides that, you can check the JUnit FAQ , where you can find a section about testing methods that return void . Often if a method doesn't return a value, it will have some side effect. Actually, if it doesn't return a value AND doesn't have a side effect, it isn't doing

I have a simple method trying to fetch some file. I would like to test when the file is none existent and this is where my problem begins. The test keeps failing. The method is something like : public Configuration populateConfigs(Configuration config) throws UnRetriableException { try { .... } catch (IOException | ConfigurationException e) { log.error(" getConfiguration : ", e); throw new UnRetriableException(e); } throw new UnRetriableException("problem getting config files."); } In my tests I have tried two separate solutions without success. Using the new style as suggested in the SO

I am new here and new to junit testing. I have a class with two methods and I want to write unit tests for it. I am not sure how to start I read some basic tutorials but I am not able to start some how. Can anyone of you provide me some basic skeleton to start with. My class is public class CreateCSV { MyWriter csvOutput = null; public void createSortedSet ( final HashMap< String, Signal > map, final long totalSize, final long totalSizewithHeader, File file ) { ArrayList< Signal > messages = new ArrayList< Signal >(); try { messages.addAll( map.values() ); map.clear(); for ( Signal signal :