ParseQuery LocalDatastore tests fail when run in isolation.
They pass when run together with the rest of the ParseQuery tests.
They fail when the ParseQuery test that call jest.dontMock('../ParseObject'); are all disabled, strong evidence that the mocks are broken and the tests only pass in the CI pipeline because the rest of the ParseObjects tests (which run before the localdatastore tests) undo them.
Steps to reproduce
Open latest alpha (aff0a00a6f5d507166dbfc14d1b695002399913b) in VSCode
npm install
Run only the tests for ParseQuery LocalDatastore
Actual Outcome
The following tests fail:
can query offline
can query offline with localId
can query offline sort multiple
can query offline select keys
Expected Outcome
The tests should pass, even when run in isolation.
Environment
Server
Parse Server version: irrelevant
Operating system: Ubuntu 22.04
Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): local
Database
System (MongoDB or Postgres): irrelevant
Database version: irrelevant
Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): irrelevant
š You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
New Issue Checklist
Issue Description
ParseQuery LocalDatastore tests fail when run in isolation.
They pass when run together with the rest of the ParseQuery tests.
They fail when the ParseQuery test that call
jest.dontMock('../ParseObject');
are all disabled, strong evidence that the mocks are broken and the tests only pass in the CI pipeline because the rest of the ParseObjects tests (which run before the localdatastore tests) undo them.Steps to reproduce
npm install
Actual Outcome
The following tests fail:
Expected Outcome
Environment
Server
Ubuntu 22.04
local
Database
Client
aff0a00a6f5d507166dbfc14d1b695002399913b
Logs