Unit testing with mongodb

problem ：

My database of choice is MongoDB. The database I chose is MongoDB.I'm writing a data-layer API to abstract implementation details from client applications - that is, I'm essentially providing a single public interface (an object which acts as an IDL). I am writing a data layer API To abstract the implementation details from the client application - in other words , I actually provide a separate public interface （ One acts as IDL The object of ）.

I'm testing my logic as I go in a TDD manner. I'm taking TDD To test my logic .Before each unit test, an @Before method is called to create a database singleton, after which, when the test completes, an @After method is called to drop the database. Before each unit test , call @Before Method to create a database singleton , after , When the test is complete , call @After Method to delete the database .This helps to promote independence among unit tests. This helps to improve the independence between unit tests .

Nearly all unit tests, ie performing a contextual query , require some kind of insertion logic to occur before hand. Almost all unit tests , namely Execute context query , All need some kind of insertion logic in advance .My public interface provides an insert method - yet, it seems incorrect to use this method as precursor logic to each unit test. My public interface provides an insertion method - However , It seems incorrect to use this method as the precursor logic of each unit test .

Really I need some kind of mocking mechanism, yet, I haven't had much experience with mocking frameworks, and it seems that Google returns nothing re a mocking framework one might use with MongoDB. I really need some sort of simulation mechanism , however , I don't have much experience with simulation frameworks , and Google It doesn't seem to return any possibility with MongoDB Simulation framework used together .

What do others do in these situations? What others have done in these situations ？That is, how do people unit test code that interacts with a database? in other words , How do people unit test code that interacts with databases ？

Also, my public interface connects to a database defined in a external configuration file - it seems incorrect to use this connection for my unit testing - again, a situation that would benefit from some kind of mocking? Besides , My public interface connects to the database defined in the external configuration file - It seems incorrect to use this connection for unit testing - Again , This situation will benefit from some kind of simulation ？

---

Solution ：

Reference resources ： https://stackoom.com/en/question/V6iP