diff options
| author | eileencodes <eileencodes@gmail.com> | 2015-06-27 10:38:45 -0400 |
|---|---|---|
| committer | eileencodes <eileencodes@gmail.com> | 2015-06-27 16:48:20 -0400 |
| commit | 4d7b50707376b09188b545043e893f275dfd84e0 (patch) | |
| tree | 7245ba3115c8419a863cef9e55e4ba5b19d7869e /actionview/lib | |
| parent | 991e98f5640874a9bda41855af4f9315aff8260a (diff) | |
| download | rails-4d7b50707376b09188b545043e893f275dfd84e0.tar.gz rails-4d7b50707376b09188b545043e893f275dfd84e0.tar.bz2 rails-4d7b50707376b09188b545043e893f275dfd84e0.zip | |
Improve error messages in cookies_test
Using `assert_predicate` and `assert_match` instead of just `assert` is
preferrable because better error messages are output.
In the case of `assert response.cookies.empty?` the error message was
`Failed assertion, no message given.` but now with `assert_predicate` it
will be `Expected {"user_name"=>"david"} to be empty?.`
For `assert_match(/user_name=david/,
response.headers["Set-Cookie"])` as well, the message returned was
unhelpful - `Failed assertion, no message given.` but now will tell what
was expected and what was returned with `Expected /user_name=david/ to
match "user_name=nope; path=/".`
Diffstat (limited to 'actionview/lib')
0 files changed, 0 insertions, 0 deletions