#225 Extract TableVerification logic from PrepAndExpectedTestCase into a separate operation so it can be used with any testing approach

[Luc Feys]

Currently the DefaultPrepAndExpectedTestCase contains logic for verifying database data against expected datasets.
This is very useful logic, but the DefaultPrepAndExpectedTestCase forces a specific flow of the test. And although it supports composition and I did not run into a blocking restriction with this approach, it would be cleaner if this verification logic would be extract into a separate 'VerifyOperation' which could be executed wherever wanted, without the additional requirements that come with using the DefaultPrepAndExpectedTestCase

[Luc Feys]

I have created a merge request for this, on which I would appreciate some feedback before continuing work on it.

[Jeff Jensen]

There are multiple refactorings I want to do with DefaultPrepAndExpectedTestCase. Extracting classes is the main one, and extracting the verifier is a good place to start.

Please see comments on the MR.

[Jeff Jensen]

Ticket moved from /p/dbunit/bugs/425/

Can't be converted:

• _fixed_release: (not fixed)
• _milestone: v2.6.*