There should be a possibility in an arquillian test to access the DatabaseConnection for additional verifications using dbunit. Using @UsingDataSet and @ShouldMatchDataSet first the already provided verifications could be done but then additional verification with dbunit using the DatabaseConnection - e.g. verfiy with a rowcount to make sure not more entries than expected have been created by the test.

Original post (with a code example): https://community.jboss.org/thread/222401?tstart=0