{"action":"closed","issue":{"url":"https://api.github.com/repos/Raynos/mercury/issues/62","labels_url":"https://api.github.com/repos/Raynos/mercury/issues/62/labels{/name}","comments_url":"https://api.github.com/repos/Raynos/mercury/issues/62/comments","events_url":"https://api.github.com/repos/Raynos/mercury/issues/62/events","html_url":"https://github.com/Raynos/mercury/issues/62","id":37801921,"number":62,"title":"outline strategy for CI","user":{"login":"neonstalwart","id":84763,"avatar_url":"https://avatars.githubusercontent.com/u/84763?v=3","gravatar_id":"","url":"https://api.github.com/users/neonstalwart","html_url":"https://github.com/neonstalwart","followers_url":"https://api.github.com/users/neonstalwart/followers","following_url":"https://api.github.com/users/neonstalwart/following{/other_user}","gists_url":"https://api.github.com/users/neonstalwart/gists{/gist_id}","starred_url":"https://api.github.com/users/neonstalwart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/neonstalwart/subscriptions","organizations_url":"https://api.github.com/users/neonstalwart/orgs","repos_url":"https://api.github.com/users/neonstalwart/repos","events_url":"https://api.github.com/users/neonstalwart/events{/privacy}","received_events_url":"https://api.github.com/users/neonstalwart/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2014-07-14T16:21:30Z","updated_at":"2015-02-06T07:15:44Z","closed_at":"2015-02-06T07:15:44Z","body":"@Raynos in https://github.com/Matt-Esch/virtual-dom/pull/90#issuecomment-48853544 you mentioned that testing mercury is a manual process currently.  this MUST become automated.\r\n\r\ni may be able to contribute towards this effort but in order to get contributions to help move towards the goal of CI, what is your plan for automated testing?  what tools and technology do you plan on using to have tests running in browsers?  even if there are currently no tests, put the mechanism in place to run tests in supported browsers so that all that's left is for tests to be written.\r\n\r\nNOTE: anything short of running tests in browsers is not sufficient - i.e. phantomjs, min-document, jsdom, etc are not enough."}}