Surface tests for CRUD and Websockets-pubsub functionality of a pod server
Note some tests are currently skipped due to https://github.com/solid/web-access-control-spec/issues/105.
Start your server with a self-signed cert on port 443 of localhost (for node-solid-server, make sure to set ACL_CACHE_TIME=5
) and run sh ./example.sh
.
In one terminal window:
npm install
$ openssl req -outform PEM -keyform PEM -new -x509 -sha256 -newkey rsa:2048 -nodes -keyout ../privkey.pem -days 365 -out ../fullchain.pem
./bin/solid-test init
export NODE_TLS_REJECT_UNAUTHORIZED=0
ACL_CACHE_TIME=0 ./bin/solid-test start
./run-against-nss.sh
configs
In another window:npm install
./run-against-nss.sh
You can also cut-and-paste the lines from run-against-nss.sh into your bash shell, then you can more easily run tests interactively.
In one terminal window:
npm ci; npm run build
./node_modules/@solid/access-token-verifier/dist/algorithm/verifySolidAccessTokenIssuer.js
to work around a bug in NSS.In another terminal window:
npm ci
./run-against-css.sh
You can also cut-and-paste the lines from run-against-css.sh into your bash shell, then you can more easily run tests interactively.
If you want to use your NSS on localhost instead of on solidcommunity.net, then:
oidcIssuer = 'https://localhost:8443';
, nssUsername = 'alice'
, and nssPassword = '123';
.NODE_TLS_REJECT_UNAUTHORIZED=0 ./bin/server.js -l debug
.NODE_TLS_REJECT_UNAUTHORIZED=0
as well, for instance:
NODE_TLS_REJECT_UNAUTHORIZED=0 node fetch.js http://localhost:3000/404.txt