This project is archived and is in readonly mode.
Use new assertion methods in test
Reported by Ben Orenstein | May 25th, 2010 @ 07:13 PM
This previous patch added two new assertions: assert_present and assert_blank.
My patch refactors several tests to use these new methods.
assert_blank foo is superior to assert foo.blank? because the former provides a more descriptive error message.
Comments and changes to this ticket
-
Ben Orenstein May 25th, 2010 @ 07:15 PM
- no changes were found...
-
Ben Orenstein May 25th, 2010 @ 08:25 PM
- Tag changed from “assertions” to “assertions, patched”
-
Ben Orenstein May 25th, 2010 @ 08:25 PM
- Tag changed from “assertions, patched” to “patched”
-
Ben Orenstein May 25th, 2010 @ 08:26 PM
- Tag changed from “patched” to “patch”
-
Santiago Pastorino February 2nd, 2011 @ 04:52 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 @ 04:52 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>
Ben Orenstein
Santiago Pastorino