{"action":"created","issue":{"url":"https://api.github.com/repos/pa11y/sidekick/issues/21","repository_url":"https://api.github.com/repos/pa11y/sidekick","labels_url":"https://api.github.com/repos/pa11y/sidekick/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/pa11y/sidekick/issues/21/comments","events_url":"https://api.github.com/repos/pa11y/sidekick/issues/21/events","html_url":"https://github.com/pa11y/sidekick/issues/21","id":156699516,"number":21,"title":"Suggestion to lean on existing CI services","user":{"login":"joecorcoran","id":65193,"avatar_url":"https://avatars.githubusercontent.com/u/65193?v=3","gravatar_id":"","url":"https://api.github.com/users/joecorcoran","html_url":"https://github.com/joecorcoran","followers_url":"https://api.github.com/users/joecorcoran/followers","following_url":"https://api.github.com/users/joecorcoran/following{/other_user}","gists_url":"https://api.github.com/users/joecorcoran/gists{/gist_id}","starred_url":"https://api.github.com/users/joecorcoran/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joecorcoran/subscriptions","organizations_url":"https://api.github.com/users/joecorcoran/orgs","repos_url":"https://api.github.com/users/joecorcoran/repos","events_url":"https://api.github.com/users/joecorcoran/events{/privacy}","received_events_url":"https://api.github.com/users/joecorcoran/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/pa11y/sidekick/labels/type:%20discussion","name":"type: discussion","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-05-25T09:09:17Z","updated_at":"2016-05-29T08:33:59Z","closed_at":null,"body":"Firstly, let me say – awesome ideas! I'm excited about the prospect of Pa11y becoming a high-profile part of software development.\r\n\r\nHaving read through [the recent announcement](http://rowanmanning.com/posts/a-new-home-for-pa11y/), it seems like the plans for Sidekick are so similar to existing continuous integration tools in a number of ways. This makes me wonder – why not lean on one of them?\r\n\r\nSince a continuous integration service (disclosure: I work for Travis CI) can already handle the `webhook –> pa11y –> post results` part of the pipeline, would it make sense to focus efforts on building an awesome pa11y dashboard that can interpret those results?\r\n\r\nThis would seem to have a number of benefits.\r\n\r\n1. Less work required from the Pa11y team\r\n1. Lean on years of acquired knowledge in a specific part of the pipeline\r\n1. Running a11y tests as part of the \"proper\" build would privilege the concept of a11y tests generally. As a separate service there is the potential for Pa11y test results to be yet another badge in the README file to be kinda ignored (\"a11y tests failed but the real tests passed, so let's deploy and fix that later\").\r\n\r\nIf you're interested in leaning on Travis for builds, for example, I'm happy to advise you along the way. What do you all think? I realise I'm coming at this with little background, so maybe I'm missing crucial details."},"comment":{"url":"https://api.github.com/repos/pa11y/sidekick/issues/comments/222349178","html_url":"https://github.com/pa11y/sidekick/issues/21#issuecomment-222349178","issue_url":"https://api.github.com/repos/pa11y/sidekick/issues/21","id":222349178,"user":{"login":"lawrencec","id":18561,"avatar_url":"https://avatars.githubusercontent.com/u/18561?v=3","gravatar_id":"","url":"https://api.github.com/users/lawrencec","html_url":"https://github.com/lawrencec","followers_url":"https://api.github.com/users/lawrencec/followers","following_url":"https://api.github.com/users/lawrencec/following{/other_user}","gists_url":"https://api.github.com/users/lawrencec/gists{/gist_id}","starred_url":"https://api.github.com/users/lawrencec/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lawrencec/subscriptions","organizations_url":"https://api.github.com/users/lawrencec/orgs","repos_url":"https://api.github.com/users/lawrencec/repos","events_url":"https://api.github.com/users/lawrencec/events{/privacy}","received_events_url":"https://api.github.com/users/lawrencec/received_events","type":"User","site_admin":false},"created_at":"2016-05-29T08:33:59Z","updated_at":"2016-05-29T08:33:59Z","body":"Great project btw!\r\n\r\nFunnily enough, I also wanted to suggest leaning on CI services. Would be good to leave the scheduling to CI and concentrate on the dashboard. That's how a lot of other services work.\r\n\r\nThere is another use case that I don't think is covered by Pa11y yet and that is running tests on pages that are part of a journey e.g pages that need to be signed in to view. That's where the advantage of running a webservice to collate the results can come in. \r\n\r\nIntegration/E2E tests (as run by CI) can run the pa11y tests at any point within the journey and ping the result to a server and a dashboard can be built from that. I helped build a page diffing dashboard tool exactly this way and we made plugins for the various functional testing frameworks, e.g webdriver, out there to integrate with the webservice. Some additional work was required to group results by journeys, builds and browsers for the dashboard but I don't think this changes your existing road plan too much. Pa11y can still be a dashboard site which accepts urls but one that also integrates with people's existing systems. \r\n\r\nIn any case, I think that the road plan should consider this use case as not enough a11y testing is done by devs or test teams and anything that can be done to lower the barrier would be helpful.\r\n\r\nNot entirely certain that my interpretation of the existing road plan was correct, so I hope I haven't got too much wrong and perhaps you considered this use case already?\r\n\r\n\r\n \r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"lawrencec"}}