Issue Overview
Problem with integration test state using transactions, @UsingDataSet and @ShouldMatchDataSet:
It seems that Arquillian Persistence does not clean up a previous test-method's setup or commit a subsequent test-method's state.
Expected Behaviour
Method 1 executes: it seeds state with @UsingDataSet, test code manipulates persistence context.
Method 2 executes subsequently: it seeds cleanly an other state with @UsingDataSet, test code manipluates persistence context and @ShouldMatchDataSet ensures database state-
Current Behaviour
With arquillian-persistence:1.2.0.2, method 2 gets a corrupted persistence state from method 1 and test code - a database insert - is not commited and thus verifyable using method 2's @ShouldMatchDataSet.
Steps To Reproduce
- Use/fork my ape-transaction-test project: https://github.com/jenskreidler/ape-transaction-test.git
- Configure project for your local enviroment (see README)
- Run
mvn clean install (uses arquillian-persistence:1.2.0.2) => UserService_IT fails
- In
pom.xml, switch arquillian-persistence to version 1.1.13.0 => UserService_IT succeeds
Additional information
Maybe this issue is related to arquillian/arquillian-extension-persistence#123 ?
Issue Overview
Problem with integration test state using transactions, @UsingDataSet and @ShouldMatchDataSet:
It seems that Arquillian Persistence does not clean up a previous test-method's setup or commit a subsequent test-method's state.
Expected Behaviour
Method 1 executes: it seeds state with @UsingDataSet, test code manipulates persistence context.
Method 2 executes subsequently: it seeds cleanly an other state with @UsingDataSet, test code manipluates persistence context and @ShouldMatchDataSet ensures database state-
Current Behaviour
With
arquillian-persistence:1.2.0.2, method 2 gets a corrupted persistence state from method 1 and test code - a database insert - is not commited and thus verifyable using method 2's @ShouldMatchDataSet.Steps To Reproduce
mvn clean install(usesarquillian-persistence:1.2.0.2) => UserService_IT failspom.xml, switcharquillian-persistenceto version1.1.13.0=> UserService_IT succeedsAdditional information
Maybe this issue is related to arquillian/arquillian-extension-persistence#123 ?