-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request: In-Memory Storage adapter for mocking unit tests #5437
Comments
I've used and contributed to some 'fake mongos' for unit testing, but I've since switched over to using mongodb-runner instead as it is fast and easy. the unit testing setup for parse-server is pretty messy, but if you look at how it is setup for the integration Parse-SDK-JS, it's pretty straight forward: https://github.com/parse-community/Parse-SDK-JS/tree/master/integration is that helpful? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
I'm bummed there isn't a "baked in" method for efficient unit testing without mongo.
Describe the solution you'd like
A clear and concise description of what you want to happen.
I'm imagining an "In-Memory" storage adapter that contains ALL of the functionality of parse without any of the unit-testing "baggage" of mongo. For example, I could "save" an object, then query for the object but the "object" is stored in RAM instead of Mongo.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Our current options for testing are:
example from @flovilmart
spin up parse server with mongo-runner -> requires additional resources and slows tests down.
I'm open to additional suggestions if anyone has any!
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: