This project is archived and is in readonly mode.
Rake tests should use the Rake api instead of call the command line directly
Reported by calavera | June 24th, 2010 @ 10:41 AM
railties/test/application/rake_test.rb calls the command line directly instead of use the Rake api to verify its behaviour. This is quite buggy because nobody guarantees to you that the rake executable that you are calling is the one that you actually want to call.
I include a patch to use the Rake api in the test rather than the rake command.
Comments and changes to this ticket
-
Santiago Pastorino February 2nd, 2011 @ 05:01 PM
- State changed from “new” to “open”
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino February 2nd, 2011 @ 05:01 PM
- State changed from “open” to “stale”
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>
calavera
Santiago Pastorino