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

Add integration test to test data-integration and compliance to the dataprofile #137

Open
SvenLieber opened this issue Sep 7, 2022 · 0 comments

Comments

@SvenLieber
Copy link
Collaborator

TL;DR several software integration tests cover the data integration and separately the corpus SPARQL query according to our dataprofile, yet another test is needed to test the combination of both.

For the dynamic generation of SPARQL queries for the data integration, we also developed integration tests. These tests contain test data and all tests succeeded for both implementations, integration based on serialized SPARQL queries and dynamically generated SPARQL queries based on a config.

However, by using the Jupyter notebook statistics of the corpus as well as the corpus Excel sheet itself we still found issues when comparing it to the older corpus version. These issues were fixed as well.

This means that our tests do not cover all important aspects yet. We have to add another test, testing not only a proper integration of identifiers, but also the resulting corpus according to the dataprofile. E.g. to verify that besides the integration based on identifiers, correct RDF properties are used and all relevant values from the source were added as well.

This can be done by e.g. reusing the dataprofile test case, i.e. test another implementation which instead of testing the dataprofile query based on already prepared integrated and source data will test the dataprofile query based on only source data and our integration scripts.

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

No branches or pull requests

1 participant