Interesting patterns there. Is the plan to follow-up with these with particular actions? That said, it seems to me a bit muddy as to what activities would best serve the responses. I suppose education/support work for those that don't feel they know *e.g.* how to use the rake/grunt entry points, or where to start on fixing flaky cucumber tests?
On Fri, 2 Sep 2016 at 03:15 Željko Filipin <[email protected]> wrote: > Survey report is now available: > > https://www.mediawiki.org/wiki/Browser_testing/User_satisfaction_survey > > Questions? Comments? > > Željko > > On Fri, Jul 1, 2016 at 5:50 PM, Željko Filipin <[email protected]> > wrote: > >> In order to improve browser testing tools, release engineering team has >> created browser testing user satisfaction survey: >> >> https://goo.gl/xS6mmV >> >> It should take you up to 5 minutes. Most of the questions have simple 5 >> level linear scale. There are 5 sections, and the last question in each >> section will be free form text field, so you can leave comments on anything >> we forgot to ask. >> >> For details about the survey, feel free to take a look at phabricator >> task: >> >> https://phabricator.wikimedia.org/T131123 >> >> Željko >> > _______________________________________________ > QA mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/qa > -- James D. Forrester Lead Product Manager, Editing Wikimedia Foundation, Inc. jforrester at wikimedia.org <https://lists.wikimedia.org/mailman/listinfo/wikimedia-l> | @jdforrester _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
