On 4/01/2019 5:59 am, Adam Kimball wrote:
I'm looking to maximize my understanding of Composer's features
related to writing, running, reporting, and testing of SHACL. The
online help docs don't appear to treat this subject much, or at least,
I couldn't find it.
Here are some basic questions:
1. Can I show conforming SHACL shapes in the SHACL Validation window?
1. I know that there is an option for showing conformance in the
Targets windows but I'm not using Targets but maybe I should be?
I never see anything in that window..
2. I know I can get the full output but then I end up with a new
graph to get rid of etc.
3. I'm just looking to approximate the experience of running unit
tests where I can see (for example) that all of my tests or suites
ran.
On the Targets View (assuming you have activated "Target View shows
conformance" in the TBC SHACL preferences), it does show the conformance
if the selected resource is a class (that is also a node shape). For the
schemashacl-violations.ttl example, I see
For an individual resource, it should help to activate the
button in the toolbar. If there are violations, you'll see something like
in the upper right corner of a resource form. Otherwise, the icon is
greyed out.
2. The new unit tests feature is awesome and I've begun to utilize it
but don't know if i have the right workflow
1. For instance, say I have existing test but want to add some
additional tests to it. It seems like the only way to do this is
to drop the test and rebuild it from the "Create a test case"
button but that leaves me a little uncertain. I really just want
to add a test, ideally in another suite. Can someone describe
their workflow for writing tests?
The workflow is different for each kind of test. Examples:
- For validation tests, use the corresponding button in the SHACL
Validation window. Note that there can only be one validation test per
file, because re-running the test means to perform validation of
everything in that graph (and in particular its imports).
- For SPARQL query tests, use "Turn into test case" from the context
menu of the SPARQL view.
- For SPARQL expression tests, highlight an expression in the SPARQL
view and right click to get "Turn into dash:FunctionTestCase".
In the latter two cases, you can define any number of tests in the same
file/graph.
There are other test case types, see the subclasses of dash:TestCase.
Which test case types are you particularly interested in?
Holger
Thanks everyone. I feel strongly that SHACL has the possibility to
really move things forward and I am excited to become expert in it.
Feel free to chime in on how YOU use the software, this isn't just for
the TQ folks.
-Adam
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "TopBraid
Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
