Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@ExpectedDataSets should cope with data subsets #7

Open
dadrus opened this issue Mar 11, 2017 · 0 comments
Open

@ExpectedDataSets should cope with data subsets #7

dadrus opened this issue Mar 11, 2017 · 0 comments

Comments

@dadrus
Copy link
Owner

dadrus commented Mar 11, 2017

As of today the implementation of @ExpectedDataSets fully relies on the comparison implementation provided by DbUnit. DbUnit however imposes a restriction: adding a new row to a table which is referenced by the expected data set but not included in it, will lead to a comparison error.
The aforementioned behavior contradicts the database bootstrapping approach. Here one would usually not only want to create the database schema, but also some initial data, which might be extended/modified by the implemented test methods. For this a further cleanup strategy might be required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant