Testing database

[mat-1]

There should be a "mock database" object (maybe saves/loads from a json file?) for running the unit tests or testing locally if you don't want to set up a MongoDB database

[frissyn]

@mat-1 Looking through some of MongoDB's docs I found mongoexport, which could be used to clone the DB to a JSON file or otherwise.

You could also deploy a public Replica Set of the DB for others to connect to for testing locally.

These are just some ideas I wanted to toss up, check em out if you like =P

[PotentialStyx]

@mat-1 Looking through some of MongoDB's docs I found mongoexport, which could be used to clone the DB to a JSON file or otherwise.

You could also deploy a public Replica Set of the DB for others to connect to for testing locally.

These are just some ideas I wanted to toss up, check em out if you like =P

The thing is we would need to remove a lot of stuff from the export/replica set, like session ids and stuff, and some of it might be needed in testing. So I think we are better off creating a json file that has the same layout/schema as the normal db but with filler content (like 3 entries, with different properties, a few fake users, and a few fake links)

[frissyn]

@mat-1 Looking through some of MongoDB's docs I found mongoexport, which could be used to clone the DB to a JSON file or otherwise.
You could also deploy a public Replica Set of the DB for others to connect to for testing locally.
These are just some ideas I wanted to toss up, check em out if you like =P

The thing is we would need to remove a lot of stuff from the export/replica set, like session ids and stuff, and some of it might be needed in testing. So I think we are better off creating a JSON file that has the same layout/schema as the normal DB but with filler content (like 3 entries, with different properties, a few fake users, and a few fake links)

I thought the objective was to create a copy of the MongoDB for users who didn't want to make their own in order to test. Making a dummy DB doesn't like it would fit that goal. Anyways, the mongo driver has to connect to a server, so even after you figure out a way to dump the DB contents to a JSON file, you still need a way to serve it locally. I don't know how to do that, but @leon332157 said he'd work on it when he gets the chance.

[PotentialStyx]

@mat-1 Looking through some of MongoDB's docs I found mongoexport, which could be used to clone the DB to a JSON file or otherwise.
You could also deploy a public Replica Set of the DB for others to connect to for testing locally.
These are just some ideas I wanted to toss up, check em out if you like =P

The thing is we would need to remove a lot of stuff from the export/replica set, like session ids and stuff, and some of it might be needed in testing. So I think we are better off creating a JSON file that has the same layout/schema as the normal DB but with filler content (like 3 entries, with different properties, a few fake users, and a few fake links)

I thought the objective was to create a copy of the MongoDB for users who didn't want to make their own in order to test. Making a dummy DB doesn't like it would fit that goal. Anyways, the mongo driver has to connect to a server, so even after you figure out a way to dump the DB contents to a JSON file, you still need a way to serve it locally. I don't know how to do that, but @leon332157 said he'd work on it when he gets the chance.

Ok, so we should host a mongo db set that is publicly writeable? If so we would still use filler values.

[selectdev]

Maybe we could implent this somehow in v3, or create a real database and just supply the url in CONTRIBUTING.md and just allow anyone to use it although it could bring some security risks