-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Improve tests #15
Comments
include the tenforce/virutoso docker container as a service in the github ci.yml however, currently just the service, not yet included in any tests #15
a simple check that the repo is connecting and querying within the Github CI environment
after the container starts, it needs just a couple of seconds to initialise. Hopefully 3s is enough to avoid any sporadic errors #15
I've made a little start on this on branch, adding the Virtuoso docker service, and a basic test that it is interacting an doing a query. These tests will fail unless the service is available, so I was thinking of checking if an environment variable is set, and otherwise skip (perhaps github sets one?) I tried adding
|
It's reasonable for tests to be be conditioned on an environment variable. See, for example, the postgres spec in the otherwise rather obsolete rdf-do gem. This environment variable can be specified in the .github/workflows/ci.yml file along with starting up the docker image. General documentation for running the specs on the desktop would be useful, too. It's not too surprising that the This typically needs some instance variables set up to allow it to work properly. For example:
Where |
check with a single select which is unlikely to change, and also include a simple insert #15
explicity setting the let(:repository) caused an infinite loop and stack overflow, because the subject is already named it works without #15
GitHub testing with virtuoso service * include virtuoso as a service in CI * include the tenforce/virutoso docker container as a service in the github ci.yml however, currently just the service, not yet included in any tests #15 * a basic integration test that does a simple query #15 * a simple check that the repo is connecting and querying within the Github CI environment * the default graph is unlikely to be needed #15 * wait 3 seconds extra, to give virtuoso service more time * after the container starts, it needs just a couple of seconds to initialise. Hopefully 3s is enough to avoid any sporadic errors #15 * rubocop on integration spec * uses not run! #15 * include it_behaves_like an RDF::Repository * try a different sleep action #15 * the previous one gave a warning * disable the it_behaves_like check for now #15 * extend tests to check the connection is working and some cleaning up * check with a single select which is unlikely to change, and also include a simple insert #15 * fixed invoking it_behaves_like but commented out until resolved * explicitly setting the let(:repository) caused an infinite loop and stack overflow, because the subject is already named it works without #15 * control whether the integration tests are run with an env variable #15 * Update spec/integration_spec.rb
From #10 (comment), more shared tests to check Repository conformance, and the set up to run tests on commit through the GitHub Actions CI task.
The text was updated successfully, but these errors were encountered: