parse-community / parse-community/parse-server-example
Failing tests on node 18.x
Open
Nobody has claimed this yet.
type:bug
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 5.3k
- PR merge metrics
- No merged PRs in 30d
Description
The provided tests in the example repo are failing on Node 18, due to a jasmine timeout error.
Steps to reproduce:
- Checkout the repository
- Setup node 18.x
- Run tests ->
npm run test
➜ parse-server-example git:(master) ✗ git --no-pager log --oneline -n 1 && node -v && npm -v && npm run test
2d072a6 (HEAD -> master, origin/master, origin/HEAD) docs: update README (#419)
v18.12.1
8.19.2
> parse-server-example@1.4.0 test
> mongodb-runner start && jasmine
◝ Starting a MongoDB deployment to test against...DATABASE_URI not specified, falling back to localhost.
Started
warn: DeprecationWarning: The Parse Server option 'directAccess' default will change to 'true' in a future version. Additionally, the environment variable 'PARSE_SERVER_ENABLE_EXPERIMENTAL_DIRECT_ACCESS' will be deprecated and renamed to 'PARSE_SERVER_DIRECT_ACCESS' in a future version; it is currently possible to use either one.
warn: DeprecationWarning: The Parse Server option 'enforcePrivateUsers' default will change to 'true' in a future version.
..F..
Failures:
1) Parse Server example failing test
Message:
Error: Timeout - Async function did not complete within 5000ms (set by jasmine.DEFAULT_TIMEOUT_INTERVAL)
Stack:
at <Jasmine>
at listOnTimeout (node:internal/timers:564:17)
at process.processTimers (node:internal/timers:507:7)
Suite error: top suite
Message:
Error: Timeout - Async function did not complete within 5000ms (set by jasmine.DEFAULT_TIMEOUT_INTERVAL)
Stack:
at <Jasmine>
at listOnTimeout (node:internal/timers:564:17)
at process.processTimers (node:internal/timers:507:7)
5 specs, 2 failures
Finished in 11.087 seconds
➜ parse-server-example git:(master) ✗
Contributor guide
No contributing guide indexed for this repository
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 checking out the repository, using Node 18.x, and running npm run test to reproduce the Jasmine timeout. Inspect the failing example-repo test and its test setup, then confirm that all 5 specs pass within the configured timeout on Node 18.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100