{"issue":{"created_at":"2011-12-08T19:58:15Z","state":"open","updated_at":"2011-12-08T21:07:13Z","comments":1,"user":{"gravatar_id":"e1aef3bc7cbb476ef2df922fb219c4a6","id":392612,"url":"https://api.github.com/users/jrnail23","avatar_url":"https://secure.gravatar.com/avatar/e1aef3bc7cbb476ef2df922fb219c4a6?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"jrnail23"},"body":"I've recently started using MSpec, and I really like it.  But as with any shiny new test/spec framework, I worry about whether or not I'm using it in a sustainable way.\r\nI'd love to see some \"best-practices\" guidance about MSpec here in the documentation.  I found a few things spread out over the interwebs, but they weren't that easy to locate, and as with any documentation, some items may be outdated (or just no longer reflective of the most up-to-date practices).","assignee":null,"id":2493617,"labels":[],"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"number":84,"title":"Please fill in \"Guidelines\" section of documentation","closed_at":null,"html_url":"https://github.com/machine/machine.specifications/issues/84","url":"https://api.github.com/repos/machine/machine.specifications/issues/84","milestone":null},"action":"created","comment":{"created_at":"2011-12-08T21:07:13Z","updated_at":"2011-12-08T21:07:13Z","user":{"gravatar_id":"e68cb40b7d3a2bb44ae50a43ddd2ff53","id":159256,"url":"https://api.github.com/users/ArnoldZokas","avatar_url":"https://secure.gravatar.com/avatar/e68cb40b7d3a2bb44ae50a43ddd2ff53?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"ArnoldZokas"},"body":"+1 That would be useful","id":3069993,"url":"https://api.github.com/repos/machine/machine.specifications/issues/comments/3069993"}}