In the package explorer unfold the class. It should show you all methods. Right click on the one method you want to run, then select Run As -> JUnit from the context menu (just tested with Eclipse 3.4.1). Also selecting “Run” on a single entry in the JUnit-results view to re-run a test works in … Read more
If you have no concrete implementations of the class and the methods aren’t static whats the point of testing them? If you have a concrete class then you’ll be testing those methods as part of the concrete class’s public API. I know what you are thinking “I don’t want to test these methods over and … Read more
For the future I would recommend Eran Harel’s answer (refactoring moving new to factory that can be mocked). But if you don’t want to change the original source code, use very handy and unique feature: spies. From the documentation: You can create spies of real objects. When you use the spy then the real methods … Read more
After using the answer from @eugene-to and another similar one here I found limitations and raised an issue on Spring: https://jira.spring.io/browse/SPR-12751 As a result, Spring test introduced the ability to register @ControllerAdvice classes in the builder in 4.2. If you are using Spring Boot then you will need 1.3.0 or later. With this improvement, if … Read more
Create and setup a “tests” folder In the Project sidebar on the left, right-click your project and do New > Directory. Name it “test” or whatever you like. Right-click the folder and choose “Mark Directory As > Test Source Root”. Adding JUnit library Right-click your project and choose “Open Module Settings” or hit F4. (Alternatively, … Read more
You can replace System.in with you own stream by calling System.setIn(InputStream in). InputStream can be a byte array: InputStream sysInBackup = System.in; // backup System.in to restore it later ByteArrayInputStream in = new ByteArrayInputStream(“My string”.getBytes()); System.setIn(in); // do your thing // optionally, reset System.in to its original System.setIn(sysInBackup); Different approach can be make this method … Read more
Call return statement anytime your test is finished and passed.
It’s deprecated because of the double’s precision problems. If you note, there’s another method assertEquals(double expected, double actual, double delta) which allows a delta precision loss. JavaDoc: Asserts that two doubles are equal to within a positive delta. If they are not, an AssertionError is thrown. If the expected value is infinity then the delta … Read more
All these answers seem overkill. You don’t add tests to make a metric tool happy. Loading a Spring context of the application takes time. Don’t add it in each developer build just to win about 0.1% of coverage in your application. Here you don’t cover only 1 statement from 1 public method. It represents nothing … Read more
Thank you for putting this outstanding question out there. For some reason, when it comes to Spark, everyone gets so caught up in the analytics that they forget about the great software engineering practices that emerged the last 15 years or so. This is why we make it a point to discuss testing and continuous … Read more