I am somewhat disappointed that JUnit5 is less predictable...
On Tue, Apr 17, 2018 at 10:35 AM, Niclas Hedhman wrote:
>
> For a while I thought the problem is that there is a hierarchy of abstract
> tests, and that there is 2 levels of inheritance between the MongoDb test
> and the AbstractPolyg
For a while I thought the problem is that there is a hierarchy of abstract
tests, and that there is 2 levels of inheritance between the MongoDb test
and the AbstractPolygeneBaseTest, but IF I do the following test, it works
import org.junit.jupiter.api.Assertions;
import org.junit.jupiter.api.Bef
Gang,
if anyone has extensive experience with JUnit5, is there any explanation
that
@Override
@BeforeEach
public void setUp()
throws Exception
{
super.setUp();
will not be called when running the test, but if I change it to
@BeforeEach
public void setUp2()
throws Exception
{
s
