From b3228bf854f3ac4cd6b9c25f0219fecb8cbc8b35 Mon Sep 17 00:00:00 2001 From: Munyoki Kilyungi Date: Tue, 10 Sep 2024 08:44:23 +0300 Subject: Create new ADR on adding RDF tests in GN3. Signed-off-by: Munyoki Kilyungi --- topics/ADR/gn3/000-add-test-cases-for-rdf.gmi | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 topics/ADR/gn3/000-add-test-cases-for-rdf.gmi (limited to 'topics/ADR/gn3/000-add-test-cases-for-rdf.gmi') diff --git a/topics/ADR/gn3/000-add-test-cases-for-rdf.gmi b/topics/ADR/gn3/000-add-test-cases-for-rdf.gmi new file mode 100644 index 0000000..deb9fa3 --- /dev/null +++ b/topics/ADR/gn3/000-add-test-cases-for-rdf.gmi @@ -0,0 +1,21 @@ +# [ADR-000/gn3] Add RDF Test Cases + +* author: bonfacem +* status: proposed +* reviewed-by: jnduli + +## Context + +We have no way of ensuring the integrity of our SPARQL queries in GN3. As such, GN3 is fragile to breaking changes when the TTL files are updated. + +## Decision + +In Virtuoso, we load all our data to a default named graph: . For SPARQL/RDF tests, we should upload test ttl files to a test named graph: , and run our end-to-end API tests against that named graph. + +## Consequences + +* Extra bootstrapping to load ttl files when running the test. +* Extra documentation to GN developers on how to run virtuoso locally to get the tests running. +* Testing against gn-machines to make sure that all things run accordingly. +* Extra maintenance costs to keep the TTL files in lockstep with the latest RDF changes during re-modeling. +* Improvement in GN3 reliability. -- cgit v1.2.3