{"action":"closed","issue":{"url":"https://api.github.com/repos/emancu/crotest/issues/5","repository_url":"https://api.github.com/repos/emancu/crotest","labels_url":"https://api.github.com/repos/emancu/crotest/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/emancu/crotest/issues/5/comments","events_url":"https://api.github.com/repos/emancu/crotest/issues/5/events","html_url":"https://github.com/emancu/crotest/issues/5","id":165197940,"number":5,"title":"Capture the exception in `assert_raise`","user":{"login":"foca","id":437,"avatar_url":"https://avatars.githubusercontent.com/u/437?v=3","gravatar_id":"","url":"https://api.github.com/users/foca","html_url":"https://github.com/foca","followers_url":"https://api.github.com/users/foca/followers","following_url":"https://api.github.com/users/foca/following{/other_user}","gists_url":"https://api.github.com/users/foca/gists{/gist_id}","starred_url":"https://api.github.com/users/foca/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/foca/subscriptions","organizations_url":"https://api.github.com/users/foca/orgs","repos_url":"https://api.github.com/users/foca/repos","events_url":"https://api.github.com/users/foca/events{/privacy}","received_events_url":"https://api.github.com/users/foca/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-07-12T22:38:52Z","updated_at":"2016-07-13T16:41:50Z","closed_at":"2016-07-13T16:41:50Z","body":"It would be useful to capture the exception in an `assert_raise` to test the message is the expected one. I'm testing the responses of a library that might return several different errors using the same subclass of `Exception`, and I would like to make sure the `err.message` is the one I should be getting.\r\n\r\nNot sure if this is doable with Crystal macros as I haven't really delved into that yet."}}
{"actor":{"display_login":"emancu"}}