[QA] Automated testing and reporting of on-wiki gadget JS errors across sites?

[Željko Filipin]

An prototype for one language would be easy, a few hours or work. The more
languages (browsers, operating systems...), the more complicated it would
become.

This sounds like a fun project. Want to pair on it?

We could timebox for 4 hours and see how far we get. (If our managers agree
that that is something we should do.) #wikidev17 would probably be a good
time to pair in-person, if both of us are there. If not, we can pair via
hangouts and/or IRC.

Željko

On Wed, Sep 21, 2016 at 7:38 PM, Andre Klapper <aklapper at wikimedia.org>
wrote:

> A clueless late night thought, probably somewhere between Pywikibot,
> Selenium, headless browsers, and helping our communities.
>
> Have some code that
> * goes to $langcode.$site.org
> * logs in on that site
> * enables all gadgets in user preferences of that sites
> * goes to a random page on that sites
> * attaches ?action=edit&debug=true to the URL
> * collects all JS error messages, deprecation warnings, and related
>   URLs for broken gadgets etc. (browser's developer tools' console)
> * knows the corresponding village pump of that site, or gathers
>   the user account who was the last editor of the affected gadget
> * posts the error message and the gadget URL on that local village
>   pump or the user talk page of the last gadget editor.
>
> Has someone tried that before?
> Do I miss any steps?
> And does that make any sense?
>
> Thanks,
> andre
> --
> Andre Klapper | Wikimedia Bugwrangler
> http://blogs.gnome.org/aklapper/
>
> _______________________________________________
> QA mailing list
> QA at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/qa
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.wikimedia.org/pipermail/qa/attachments/20160926/dab5ddcf/attachment.html>