npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@zazuko/shacl-test

v0.1.1

Published

Runs SHACL shapes against a set of positive and negative test cases (data graphs).

Downloads

126

Readme

SHACL-test

Runs SHACL shapes against a set of positive and negative test cases (data graphs).

Positive test cases are a simple fail/pass. Negative test cases are expected to fail and the validation report is compared against the expectation using approvals.

In case of failures, a SHACL Playground link is provided for further investigation.

Usage

npx shacl-test \
  --shapes=${SHAPES} \
  --valid-cases="${VALID_CASES_GLOB}" \
  --invalid-cases="${INVALID_CASES_GLOB}" \
  --filter="${FILTER}" \
  --approve \
  --debug \
  --prefixes=${PREFIXES} \
  --command="${COMMAND}"

Only the --shapes option is required. The rest are optional.

--shapes can be a filesystem path or URL and include code:imports.

--valid-cases and --invalid-cases are globs that match the test cases. Make sure to put them in quotes to avoid shell expansion.

--filter is a regular expression to filter the test cases.

--approve will approve the validation reports for the negative test cases instead of failing.

--debug will print the validation report for each test case.

--prefixes is a comma-separated list of prefix declarations to be used in the SHACL shapes. For example, --prefixes=schema,qudt,cube=https://cube.link/, will declare the prefixes schema, qudt and cube with the respective URIs. In the case of schema and qudt, their URIs are taken from the list provided by the @zazuko/prefixes package (and, by extension, the Zazuko prefix server).

--command is a command to run for each test case. It will be passed the shapes path as argument and the test case on standard input. The default is npx barnard59 shacl validate --shapes, which translates to npx barnard59 shacl validate --shapes ${shapes} < $testCase. The script must return a non-zero exit code if the test case is invalid.