JUnit in version 4.x is a test framework which uses annotations to identify methods that specify a test. Typically a JUnit test is a method contained in a class which is only used for testing. This is called a Test class. To write a test with the JUnit 4.x framework you annotate a method with … Read more
Using the built in equals for this kind of test is a bad idea for a couple of reasons: As you can see here, a test failure doesn’t give you the diagnostics that you want to actually figure out why the objects are different If you’re implementing equals purely for the test, if it changes … Read more
Upcasting is always a codesmell and should be avoided. Usually it is needed because the code design violated the Tell, don’t ask! principle. Just guessing: In your case the “procution code” always passes instaces of class A so that it works. But your test obviously sets up a class B object (at some point you … Read more
Unittests in general test public observable behavior in your case it is the interaction with the two streams. create mocks for the two steams (usually I’d suggest to use a mocking framework but there are some simple implementations in the standard lib quite suitable for this purpose…) Configure the inputStream to return data in false … Read more