OK resolved... For anyone who comes up against this in future...
SecurityUtils.getSubject() in test B was the subject from the previous test A !! Eclipse runs tests in different threads - I always assumed Maven command line did the same... but it seems to be a single test thread ... Anyway I was able to run tests with: %>mvn -DforkMode=always test And the problem went away I need to look at Maven using a single test thread a bit more - -- View this message in context: http://n2.nabble.com/Shiro-error-on-JUnit-test-tp4755410p4755567.html Sent from the Shiro User mailing list archive at Nabble.com.
