{"action":"created","issue":{"url":"https://api.github.com/repos/fscheck/FsCheck/issues/162","labels_url":"https://api.github.com/repos/fscheck/FsCheck/issues/162/labels{/name}","comments_url":"https://api.github.com/repos/fscheck/FsCheck/issues/162/comments","events_url":"https://api.github.com/repos/fscheck/FsCheck/issues/162/events","html_url":"https://github.com/fscheck/FsCheck/pull/162","id":109873370,"number":162,"title":"Migrate from xunit assertions to unquote","user":{"login":"ploeh","id":242165,"avatar_url":"https://avatars.githubusercontent.com/u/242165?v=3","gravatar_id":"","url":"https://api.github.com/users/ploeh","html_url":"https://github.com/ploeh","followers_url":"https://api.github.com/users/ploeh/followers","following_url":"https://api.github.com/users/ploeh/following{/other_user}","gists_url":"https://api.github.com/users/ploeh/gists{/gist_id}","starred_url":"https://api.github.com/users/ploeh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ploeh/subscriptions","organizations_url":"https://api.github.com/users/ploeh/orgs","repos_url":"https://api.github.com/users/ploeh/repos","events_url":"https://api.github.com/users/ploeh/events{/privacy}","received_events_url":"https://api.github.com/users/ploeh/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":18,"created_at":"2015-10-05T19:55:12Z","updated_at":"2015-10-07T11:43:51Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/fscheck/FsCheck/pulls/162","html_url":"https://github.com/fscheck/FsCheck/pull/162","diff_url":"https://github.com/fscheck/FsCheck/pull/162.diff","patch_url":"https://github.com/fscheck/FsCheck/pull/162.patch"},"body":"Addresses #160 \r\n\r\nA couple of comments:\r\n\r\n- There's more than one way to express many of the assertions with Unquote. As you can tell, I tend to favour the built-in operators `=!` and `<>!` over `test <@ ... @>` in most cases. It would, however, also be possible to stick more consistently with the `test <@ ... @>` style. Let me know if I should change that.\r\n- With the built-in operators `=!` and `<>!`, the assertions become so terse that they almost 'drown' in the test. If we stick with these operators, I would recommend adopting this heuristic for formatting tests: http://blog.ploeh.dk/2013/06/24/a-heuristic-for-formatting-code-according-to-the-aaa-pattern"},"comment":{"url":"https://api.github.com/repos/fscheck/FsCheck/issues/comments/146165877","html_url":"https://github.com/fscheck/FsCheck/pull/162#issuecomment-146165877","issue_url":"https://api.github.com/repos/fscheck/FsCheck/issues/162","id":146165877,"user":{"login":"ploeh","id":242165,"avatar_url":"https://avatars.githubusercontent.com/u/242165?v=3","gravatar_id":"","url":"https://api.github.com/users/ploeh","html_url":"https://github.com/ploeh","followers_url":"https://api.github.com/users/ploeh/followers","following_url":"https://api.github.com/users/ploeh/following{/other_user}","gists_url":"https://api.github.com/users/ploeh/gists{/gist_id}","starred_url":"https://api.github.com/users/ploeh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ploeh/subscriptions","organizations_url":"https://api.github.com/users/ploeh/orgs","repos_url":"https://api.github.com/users/ploeh/repos","events_url":"https://api.github.com/users/ploeh/events{/privacy}","received_events_url":"https://api.github.com/users/ploeh/received_events","type":"User","site_admin":false},"created_at":"2015-10-07T11:43:51Z","updated_at":"2015-10-07T11:43:51Z","body":"Uh-oh, it's almost like we flipped a switch. Now the AppVeyor build succeed, but the Travis build failed... :disappointed: "}}