-
-
Notifications
You must be signed in to change notification settings - Fork 379
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
[e2e tests for mongo-sample] #1037
Comments
An e2e test usually should be using a database, that way you are testing the entire flow, from the request coming in, to the data being saved, to the data being retrieved. Usually it's also preferable to use a different database for testing that your dev or production database to ensure you don't have any collisions or pollution of your database. I can try to add an e2e sample for mongo though |
Hey guys :) @jmcdo29 well done with the repo! Thought about adding this e2e test, from the controller to an in-memory DB, what do you think? |
@omermorad thanks for looking to continue! You can either use an in memory database, or you can add the mongo image to the docker-compose. Either way I look forward to the contribution |
Great, I will work on something and send you a PR |
Should I modify this test? Or work on a new one? |
Add a new |
Just a e2e tests using mongo
A clear and concise description of what feature you want to be shown tests for (e.g. Authentication):
I tried to create e2e tests by when i started it it's connected to db and adding this data from tests to my db. Should i use mockingoose?
The text was updated successfully, but these errors were encountered: