@Transactional(rollbackOnly = true) is bypassed running tests through TestSuite

[danielemaddaluno]

I've found a strange behavior using @Transactional(rollbackOnly = true) on method of Test classes used inside a JUnitTestSuite:

I've tried to reproduce this problem inside the mybatis-cdi project forked but I didn't manage to.

So to reproduce the problem I'll refer to my example-project.
I've created two suites:

• JunitTestSuiteWriteWorking (it has a single class in the suite) → in this the transactional is considered.
• JunitTestSuiteWriteNotWorking (composed of two test classes) → in this the transactional is completely ignored.

I expected to run without any error both of them without errors (with an empty test table), but only the first one works fine.
The @Transactional(rollbackOnly = true) on the method UserMapperTestReadWrite.t1_insert is considered only on the first suite, in the second one it is completely bypassed.

Individually each class referred from the suites runs with no errors and failures.

[mnesarco]

Hi @danielemaddaluno , this is a very strange case, but it is maybe more related to your Test environment than to mybatis-cdi itself. Also this is a very old issue without more details. I am closing this, if you have more info and are still interested, please reopen this.