-
Notifications
You must be signed in to change notification settings - Fork 0
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
Test data for development #5
Comments
We all use the same database, even when running offline? (Help me out here @meg768) Anyway, it should be possible to create a database with fake content, so if @mounte wants to start this, its a good idea. Further on we want to add any number of (fake) reservations for load testing and simulating volume usage. |
I will look into seeding database after the weekend. |
I will add your e-mail (daniel@bookio.com) as a user to my test database, if you then login (www.bookio.com/booker) you can see the data i use. Maybe the scripts should build this database from scratch? On 15 jan 2014, at 23:16, Daniel Wedlund notifications@github.com wrote:
|
Thank you very much. Kövecses-Varga Dániel
|
When developing using offline database there are some missing data that currently affect the behaviour of the application (for instance missing icons in the database ==> javascript error etc.)
I suggest that some database population code should be added (as a rake task or via the db/seeds.rb) (to some extent one could use faker and populator, see: http://railscasts.com/episodes/126-populating-a-database) so we know that when running db:create db:migrate db:seed (or db:create db:migrate bookio:populatedev) we all have the same environment.
Since I just started reviewing and getting to know the code I dont think I am the right person to do so in the most efficient way but on the otherside it might be a good "first" task for me.
What do you say? Or am I totally on the wrong side of this, maybe you already have some seeding-script hanging around that I couldnt find :)
The text was updated successfully, but these errors were encountered: