-
-
Notifications
You must be signed in to change notification settings - Fork 6
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 tests for federated SPARQL queries between the curies mapping service and popular triplestores #53
base: main
Are you sure you want to change the base?
Add tests for federated SPARQL queries between the curies mapping service and popular triplestores #53
Conversation
…rvice and popular triplestores properly work. Triplestores need to be deployed locally before running the tests with docker compose, if the triplestores are not deployed the tests for federated queries will be ignored. Added: - a docker-compose.yml to deploy the bioregistry, blazegraph and virtuoso - a resources/ folder in tests which contains the Dockerfile for the curies mapping service used for testing, and an init script for the triplestores - a step to start and init the triplestores in the gh action for testing - instructions to start the triplestores with docker compose in the readme - a tests/test_sparql.py file with 4 tests of federated queries using `SERVICE`: from virtuoso to curies, from blazegraph to curies, from curies to virtuoso, from curies to blazegraph
Codecov Report
@@ Coverage Diff @@
## main #53 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 9 9
Lines 501 501
Branches 104 102 -2
=========================================
Hits 501 501
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
…e is still failing due to an issue when extracting the sparql vars
blazegraph: | ||
image: metaphacts/blazegraph-basic:2.2.0-20160908.003514-6-jetty9.4.44-jre8-45dbfff | ||
ports: | ||
- 8889:8080 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there a reason we can't just use the default ports for each service as we expose outside of docker?
Add tests to check if federated queries between the curies mapping service and popular triplestores properly work.
Triplestores need to be deployed locally before running the tests with docker compose, if the triplestores are not deployed the tests for federated queries will be skipped
Added:
docker-compose.yml
to deploy the bioregistry, blazegraph and virtuosoresources/
folder in tests which contains the Dockerfile for the curies mapping service used for testing, and an init script for the triplestoresSERVICE
: from virtuoso to curies, from blazegraph to curies, from curies to virtuoso, from curies to blazegraph