nodeSolidServer / nodeSolidServer/node-solid-server

Failing tests in `solid-contrib/solid-crud-tests`

Open
#1,736 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.8k
Forks
308
PR merge metrics
No merged PRs in 30d

Description

During the testing process on https://solid-crud-tests-example-1.solidcommunity.net, several tests have unfortunately not yielded successful results.

The tests in question specifically pertain to the Notification and Storage categories. To provide a concise overview:

FAIL  test/surface/notifications.test.ts
Notifications
When overwriting plain text with plain text using PUT
  ✕ WPS  insecure websockets-pubsub advertised using Updates-Via Link header (11 ms)
  ✓ WPS  emits insecure websockets-pubsub on the resource (1 ms)
  ✕ SECURE_WEBSOCKETS  secure websockets advertised using server-wide or resource-specific Link header (3 ms)
  ✓ SECURE_WEBSOCKETS  emits secure websockets notification on the resource
  ✕ WEBHOOKS  webhooks advertised using server-wide or resource-specific Link header (1 ms)
  ✕ WEBHOOKS  emits webhook notification on the resource (1 ms)
 

FAIL  test/surface/fetch-pod-root.test.ts
Alice's storage root
  ✕ is an ldp BasicContainer (3 ms)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the failures in test/surface/notifications.test.ts and test/surface/fetch-pod-root.test.ts against the solid-crud-tests example server. Read the failing Notification and Alice's storage root cases to identify why the advertised links, emitted notifications, and container response differ from expectations. Done means the listed tests pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.