This project is archived and is in readonly mode.
Providing wrong password for development database causes skipping of unit tests
Reported by ronin-35527 (at lighthouseapp) | November 21st, 2008 @ 09:38 AM | in 2.x
If you provide a wrong password for your development database in database.yml rake will skip the unit tests and jump straight to functional tests when running 'rake test' without further notice. I guess the issue appears because rake is unable to copy the structure of the development database into the testing database. This is a problem because rake might end up running tests that is written for a newer version of the database - with an old version of it.
To recreate the issue just try typing something like "sifsidofgisno" in database.yml under development, and then run 'rake test'. No error messages, rake just skips the unit tests.
Comments and changes to this ticket
-
ronin-35527 (at lighthouseapp) December 15th, 2008 @ 07:11 PM
- Title changed from “Providing wrong password for development database causes bypassing of unit tests” to “Providing wrong password for development database causes skipping of unit tests”
-
Pratik March 7th, 2009 @ 02:27 PM
- State changed from “new” to “wontfix”
Provide a correct password or a patch :)
Thanks.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Pratik