search

Ragnyll / FridgeFiller

Our Project For CS 4096
1 stars 1 forks source link

Some Form of Database Persistence #17

Open Ragnyll opened 8 years ago

Ragnyll commented 8 years ago

Since we aren't maintaining the database from our github repo then we should probably have some sort of script to make sure everyone has the same mock data.

This could probably be implemented as a python file that just has the django commands that stick everything in the database. We could have a text file (or json file or something) that has all the data that the file would access.

There might be an easier way of doing this that someone might know, but I'm just throwing this out there

jonsimington commented 8 years ago

Let's go with a python file that creates an object or several objects for each model, and throw that in a scripts folder in the project root. From there, we can make a start.sh script that starts the django test server and runs the python file to fill the database.

brandonphelps commented 8 years ago

This is what the fixtures are for.

brandonphelps commented 8 years ago

Can even make a unit test like functionality for checking the api.

jonsimington commented 8 years ago

See #25

jonsimington commented 8 years ago

@brandonphelps Can you make some more fixtures? At least 2 lists for each dummy user, and lots of items to populate those lists / items to create new lists