named_seeds 1.0.3 → 1.0.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/CHANGELOG.md +5 -0
- data/README.md +3 -1
- data/lib/named_seeds/railties/databases.rake +1 -0
- data/lib/named_seeds/version.rb +1 -1
- metadata +1 -1
data/CHANGELOG.md
CHANGED
data/README.md
CHANGED
@@ -36,9 +36,11 @@ Use the `NamedSeeds.identify` method to give a name to the identity used for thi
|
|
36
36
|
|
37
37
|
### Rake Files
|
38
38
|
|
39
|
+
**Using these tasks manually should not be needed as both are hooked into the proper `test:prepare` and `db:setup` process for you.**
|
40
|
+
|
39
41
|
NamedSeeds includes two rake tasks. The `db:test:seeds` is the one that does all the work and is automatically called after Rails' `test:prepare` for you. So running your rake test tasks will create your test database and seed it for you automatically before your tests run.
|
40
42
|
|
41
|
-
The other task is `db:development:seed`. This task invokes the normal Rails' `db:seed` task, then loads the db/test/seeds.rb file while still in development mode.
|
43
|
+
The other task is `db:development:seed`. This task invokes the normal Rails' `db:seed` task, then loads the db/test/seeds.rb file while still in development mode. We automatically call this task after `db:setup` for you. This task provides a way for a developer to populate their development database with the same fixture story used for testing. This makes it easy for developers to learn your application as the test story is a 1 to 1 mapping of data in local development.
|
42
44
|
|
43
45
|
```shell
|
44
46
|
$ rake db:test:seed # Run the seed data from db/test/seeds.rb and
|
data/lib/named_seeds/version.rb
CHANGED