Arquillian starts up.. even when the test doesn't require it?

[meetoblivion]

I ran into a weird issue.  We're working on some enahncements to an existing GFV3 application and I figured "ok, let me throw arquillian in since we're looking for test automation"

I just noticed that when the tests execute, the arquillian enriched tests cause the server to start AND the plain JUnit tests cause the server to start.  Is this normal?

[aslak]

If your test suite contains a class with @RunWith(Arquillian.class) it will start, but it shouldn't if it doesn't..  ?

[meetoblivion]

It looks like in my case, the oddity is that an embedded gf 3.0.1 starts up prior to the test cases.  I reran the test suite a few times to be sure, ended up piping the output through netbeans to verify.  Should it?

[aslak]

It shouldn't start befor you run the testcases, but in JUnit, all the TestCases are passed to the Runner(Arquillian) for initialization before it starts executing @Test. It's in this phase the server is started. if that's what you mean?