{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/citgm/issues/13","labels_url":"https://api.github.com/repos/nodejs/citgm/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/citgm/issues/13/comments","events_url":"https://api.github.com/repos/nodejs/citgm/issues/13/events","html_url":"https://github.com/nodejs/citgm/issues/13","id":103081705,"number":13,"title":"`npm smoketest`","user":{"login":"jasnell","id":439929,"avatar_url":"https://avatars.githubusercontent.com/u/439929?v=3","gravatar_id":"","url":"https://api.github.com/users/jasnell","html_url":"https://github.com/jasnell","followers_url":"https://api.github.com/users/jasnell/followers","following_url":"https://api.github.com/users/jasnell/following{/other_user}","gists_url":"https://api.github.com/users/jasnell/gists{/gist_id}","starred_url":"https://api.github.com/users/jasnell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jasnell/subscriptions","organizations_url":"https://api.github.com/users/jasnell/orgs","repos_url":"https://api.github.com/users/jasnell/repos","events_url":"https://api.github.com/users/jasnell/events{/privacy}","received_events_url":"https://api.github.com/users/jasnell/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-08-25T17:55:19Z","updated_at":"2015-09-02T15:08:07Z","closed_at":null,"body":"I'm considering the possibility of adding a support for a `npm smoketest` convention. Essentially, if module developers want to include a `smoketest` script in their package.json as an alternative to `npm test`, then `citgm` would choose to run that as an alternative. Doing so would allow module developers to create subsets of the tests that make the most sense for smoke testing, or perform additional set up that may be necessary independently of the normal test suite. "},"comment":{"url":"https://api.github.com/repos/nodejs/citgm/issues/comments/137117757","html_url":"https://github.com/nodejs/citgm/issues/13#issuecomment-137117757","issue_url":"https://api.github.com/repos/nodejs/citgm/issues/13","id":137117757,"user":{"login":"jasnell","id":439929,"avatar_url":"https://avatars.githubusercontent.com/u/439929?v=3","gravatar_id":"","url":"https://api.github.com/users/jasnell","html_url":"https://github.com/jasnell","followers_url":"https://api.github.com/users/jasnell/followers","following_url":"https://api.github.com/users/jasnell/following{/other_user}","gists_url":"https://api.github.com/users/jasnell/gists{/gist_id}","starred_url":"https://api.github.com/users/jasnell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jasnell/subscriptions","organizations_url":"https://api.github.com/users/jasnell/orgs","repos_url":"https://api.github.com/users/jasnell/repos","events_url":"https://api.github.com/users/jasnell/events{/privacy}","received_events_url":"https://api.github.com/users/jasnell/received_events","type":"User","site_admin":false},"created_at":"2015-09-02T15:08:07Z","updated_at":"2015-09-02T15:08:07Z","body":"@smartmouse ... not so much yet. At the very least, some kind of consistent output for the tests themselves would be ideal. A package published to npm could include a minimal smoketest script that can help citgm bootstrap things so that the package doesn't have to publish it's tests to npm and we don't have to go hunting around github for the right version, etc. We'd have to work out exactly what that process would be tho"}}