{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/node/issues/3872","labels_url":"https://api.github.com/repos/nodejs/node/issues/3872/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/node/issues/3872/comments","events_url":"https://api.github.com/repos/nodejs/node/issues/3872/events","html_url":"https://github.com/nodejs/node/issues/3872","id":117290885,"number":3872,"title":"Should there be a Testing WG?","user":{"login":"Trott","id":718899,"avatar_url":"https://avatars.githubusercontent.com/u/718899?v=3","gravatar_id":"","url":"https://api.github.com/users/Trott","html_url":"https://github.com/Trott","followers_url":"https://api.github.com/users/Trott/followers","following_url":"https://api.github.com/users/Trott/following{/other_user}","gists_url":"https://api.github.com/users/Trott/gists{/gist_id}","starred_url":"https://api.github.com/users/Trott/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Trott/subscriptions","organizations_url":"https://api.github.com/users/Trott/orgs","repos_url":"https://api.github.com/users/Trott/repos","events_url":"https://api.github.com/users/Trott/events{/privacy}","received_events_url":"https://api.github.com/users/Trott/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nodejs/node/labels/discuss","name":"discuss","color":"02d7e1"},{"url":"https://api.github.com/repos/nodejs/node/labels/test","name":"test","color":"990099"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":18,"created_at":"2015-11-17T06:17:28Z","updated_at":"2015-12-02T16:28:56Z","closed_at":null,"body":"Would it be useful to have a Testing WG? Things a WG might do:\r\n\r\n* OMG fix all those flaky tests.\r\n* Create some guidelines around tests. (For example, when should a file containing multiple tests be split into multiple files?)\r\n* Maybe work with the Build WG on the issue of buildbot failures, although I suspect the Build WG is all over that problem. (But just in case: Is there a way to test for buildbot failures? Automate notification to relevant parties so they can be fixed promptly? Is there a way to automate retry when a buildbot fails? Maybe a Test WG can be given limited privileges on the CI infrastructure such that the tedious/mechanistic elements of dealing with buildbot failures can be delegated to them?)\r\n* Maybe see about porting as much of the Python test harness code to Node as is sensible.\r\n\r\nAnyone interested?"},"comment":{"url":"https://api.github.com/repos/nodejs/node/issues/comments/161355566","html_url":"https://github.com/nodejs/node/issues/3872#issuecomment-161355566","issue_url":"https://api.github.com/repos/nodejs/node/issues/3872","id":161355566,"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-12-02T16:28:56Z","updated_at":"2015-12-02T16:28:56Z","body":"@mikeal ...a testing team seems like a good place to start. Who should be the initial members, I'll get the team created."}}