[QA] annotating browser test failures

Mon Jun 2 21:50:11 UTC 2014

My browsertests QA interaction is
* go look at my project's cloudbees dashboard, e.g.
https://wmf.ci.cloudbees.com/view/flow/
* click a failed test run,
* look at the graph to see if it's gone up
* If it has, do some investigation

My frustration has been, whatever I figure out isn't shared with others,
and vice versa. I could ask on IRC but people are busy and in other
timezones. I could send an e-mail, or file a bug, but neither of those
directly helps the next person to go through this process. It's
demotivating and un-wiki-like.

I just realized that if you login to cloudbees, you can edit the
descriptions of each Build, Test Result, and individual tests!

If you edit the Test Result description of a failed build with what you
figure out, then everyone will see it in the Build History log at the
bottom left; also when viewing a Test Result you can click History to see
previous notes. It's no longer a solitary struggle against a de-motivating
graph of red spikes with occasional green sunny skies, it becomes a
conversation, a shared quest.

I think we should encourage doing this!  I added it to <
https://www.mediawiki.org/wiki/Quality_Assurance/Browser_testing#How_to_contribute>.
I don't know how many QA people have cloudbees accounts.

BTW, this is using the classic cloudbees UI. Cloudbees has a tab [β Try our
new UI] but when I click it I can't figure out where the dashboards are.

Cheers fellow quest-ers,
--
=S Page  Features engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/qa/attachments/20140602/e00c9d35/attachment.html>