This project is archived and is in readonly mode.
Rake test task looks at wrong database
-
Pratik"I would expect that testing tasks could run without the other databases present..."
Me too.
-
andyjeffries- Tag changed from 2.2, db, rake, testing to 2.2, db, patch, rake, testing
I'm very new to Rails development, but I've had a quick play with this locally and it seems as simple as a one-line patch.
Can someone test it out and let me know if this works.
Also, I couldn't find any tests for Rake tasks so I'm not aware of where to put a test to prove this works (I'm new to testing Rake tasks).
-
Michael Koziarskidb:test:prepare will copy the values over from development to test after running those migrations though. So if there are pending migrations in development you'll get the wrong behaviour.
-
CancelProfileIsBroken- Tag changed from 2.2, db, patch, rake, testing to 2.2, bugmash, db, patch, rake, testing
-
Nick Quaranto- This seems like a strange use case, I can see it maybe for CI servers and the like, but it doesn't seem helpful enough for normal development.
-
Nick Quaranto
That was a minus 1. Seems like LH likes to eat my formatting.
-
Dan Pickett-1 on this as well - I think this is something that we might want to address in 3, but I don't identify it as critical to 2.x - in the use case of CI, I just create the dev database so prepare will run successfully
-
CancelProfileIsBroken
- State changed from new to wontfix
- Tag changed from 2.2, bugmash, db, patch, rake, testing to 2.2, db, patch, rake, testing
No one has come up with a good workaround for the issue Koz raised. We can reopen if someone has a brainstorm.
