nodeSolidServer / nodeSolidServer/node-solid-server
Assertions in async callbacks will not mark tests as failed
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
Looking through the tests for NSS I see some that don't appear to actually achieve anything (unless I'm missing something).
Some of them have been marked to skip, which is fair enough.
For example:
https://github.com/solid/node-solid-server/blob/master/test/integration/ldp-test.js#L178
https://github.com/solid/node-solid-server/blob/master/test/integration/ldp-test.js#L199
https://github.com/solid/node-solid-server/blob/master/test/integration/ldp-test.js#L214
https://github.com/solid/node-solid-server/blob/master/test/integration/ldp-test.js#L326 (This one isn't skipped)
If they're in tests like that, there could be a possibility that it's leaked into NSS itself as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the async test cases in test/integration/ldp-test.js at lines 178, 199, 214, and 326. Check how assertions inside their callbacks are handled, then inspect related NSS test code for the same pattern. Done means the affected tests reliably report assertion failures instead of passing silently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100