<div dir="ltr"><br><div>Just FYI, the information about setting up Vagrant from the training session July 18 is out of date, current documentation is at <a href="http://www.mediawiki.org/wiki/Vagrant">http://www.mediawiki.org/wiki/Vagrant</a> . I've been working with vagrant earlier this week so I can vouch that it is accurate now. </div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 16, 2013 at 7:41 AM, Justin Rohrman <span dir="ltr"><<a href="mailto:rohrmanj@gmail.com" target="_blank">rohrmanj@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>This sounds like a great idea to me. The timing would certainly be tight but I think with the VMs and Vagrant usage we should be good. I'll ping Michael and see what he thinks.</div>
<div><br></div><br>
<div class="gmail_extra">Date: Thu, 15 Aug 2013 14:12:08 -0700<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
From: Chris McMahon <<a href="mailto:cmcmahon@wikimedia.org" target="_blank">cmcmahon@wikimedia.org</a>><br>
To: "QA (software quality assurance) for Wikimedia projects."<br>
<<a href="mailto:qa@lists.wikimedia.org" target="_blank">qa@lists.wikimedia.org</a>><br>
Subject: Re: [QA] Weekend testing americas on September 7th<br>
Message-ID:<br></div>
<<a href="mailto:CAJohBHTurqx7G5EhK1Q2Ant%2BgTFZP4gPvqJ3XjzH2_x2fskRZg@mail.gmail.com" target="_blank">CAJohBHTurqx7G5EhK1Q2Ant+gTFZP4gPvqJ3XjzH2_x2fskRZg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<div><div class="h5"><br>
<br>
On Thu, Aug 15, 2013 at 6:43 AM, Justin Rohrman <<a href="mailto:rohrmanj@gmail.com" target="_blank">rohrmanj@gmail.com</a>> wrote:<br>
<br>
> Let's hear it :)<br>
><br>
<br>
Here goes...<br>
<br>
There is a certain tension in the testing community between advocates for<br>
UI/browser test automation and advocates for human "sapient" testing. I'd<br>
like to go there.<br>
<br>
Specifically, I'd like to do this with Weekend Testing:<br>
<br>
* Pick a complex feature for which browser test automation exists. Right<br>
now I'm thinking CirrusSearch or VisualEditor. Because we're using<br>
Cucumber, the test Scenarios should be understandable by people who are not<br>
programmers. Because we're using the page_object Ruby gem, the guts of the<br>
tests should be readable by people with programming experience in just<br>
about any language. Regardless of level of expertise, we should be able<br>
to provide everyone a local test environment from which to run the<br>
automated tests against WMF hosts either natively or with a VirtualBox VM<br>
configured via vagrant (<a href="http://www.mediawiki.org/wiki/Vagrant" target="_blank">http://www.mediawiki.org/wiki/Vagrant</a>). We have<br>
done this before:<br>
<br>
online: <a href="https://www.mediawiki.org/wiki/Meetings/2013-07-18" target="_blank">https://www.mediawiki.org/wiki/Meetings/2013-07-18</a><br>
live: <a href="https://www.mediawiki.org/wiki/Meetings/2013-06-27" target="_blank">https://www.mediawiki.org/wiki/Meetings/2013-06-27</a><br>
<br>
Given a robust set of automated browser tests and the ability to run them,<br>
let us then:<br>
<br>
* Identify deficiencies in the automated test coverage for the feature.<br>
This may or may not include analysis of the test code itself, but would<br>
certainly at least include analysis of the ATDD-style stated feature<br>
coverage in the Cucumber Scenarios. Do we have any technical debt in our<br>
test code?<br>
<br>
* Identify test charters for which automated testing is not possible and<br>
which are only testable by actual human beings. Are there tests that<br>
cannot be automated, and is such testing worthwhile?<br>
<br>
Outcomes:<br>
<br>
* Participants will be able to analyze ATDD-style automated browser tests<br>
* Participants will be able to run Cucumber + page_object browser tests and<br>
analyze the results of those tests<br>
* Participants will be able to demonstrate automated browser test practices<br>
with examples from the open WMF browser test code<br>
* Participants will be able to begin to contribute to WMF testing efforts<br>
if they wish, whether automated or not<br>
<br>
This might be too ambitious. I'm pretty sure this would be the most<br>
technically challenging session in the history of WTA. OTOH, we've already<br>
built the infrastructure to do this kind of thing, let's spread the word<br>
about what is possible.<br>
<br>
-Chris<br>
<br>
<br>
<br>
><br>
> Message: 2<br>
>> Date: Wed, 14 Aug 2013 08:56:54 -0700<br>
>> From: Chris McMahon <<a href="mailto:cmcmahon@wikimedia.org" target="_blank">cmcmahon@wikimedia.org</a>><br>
>> To: "QA (software quality assurance) for Wikimedia projects."<br>
>><br>
>> <<a href="mailto:qa@lists.wikimedia.org" target="_blank">qa@lists.wikimedia.org</a>><br>
>> Subject: Re: [QA] Weekend testing americas on September 7th<br>
>> Message-ID:<br>
>> <<br>
>> <a href="mailto:CAJohBHQzWK5H9weGS-SERHe0faZRSS08WjiGw-UNb7ABe-xC0w@mail.gmail.com" target="_blank">CAJohBHQzWK5H9weGS-SERHe0faZRSS08WjiGw-UNb7ABe-xC0w@mail.gmail.com</a>><br>
>> Content-Type: text/plain; charset="iso-8859-1"<br>
>><br>
>><br>
>> I actually have an idea that I think would be of interest to WTA and of<br>
>> benefit to WMF, but I'd like to encourage others to reply first..<br>
>><br>
>> -C<br>
>><br>
>><br>
>><br>
>><br>
> _______________________________________________<br>
> QA mailing list<br>
> <a href="mailto:QA@lists.wikimedia.org" target="_blank">QA@lists.wikimedia.org</a><br>
> <a href="https://lists.wikimedia.org/mailman/listinfo/qa" target="_blank">https://lists.wikimedia.org/mailman/listinfo/qa</a><br>
><br>
><br></div></div>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wikimedia.org/pipermail/qa/attachments/20130815/e6688311/attachment-0001.html" target="_blank">http://lists.wikimedia.org/pipermail/qa/attachments/20130815/e6688311/attachment-0001.html</a>><br>
<br>
------------------------------<div class="im"><br>
<br>
_______________________________________________<br>
QA mailing list<br>
<a href="mailto:QA@lists.wikimedia.org" target="_blank">QA@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/qa" target="_blank">https://lists.wikimedia.org/mailman/listinfo/qa</a><br>
<br>
<br></div>
End of QA Digest, Vol 4, Issue 13<br>
*********************************<br>
</blockquote></div><div><br></div>
</div></div>
<br>_______________________________________________<br>
QA mailing list<br>
<a href="mailto:QA@lists.wikimedia.org">QA@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/qa" target="_blank">https://lists.wikimedia.org/mailman/listinfo/qa</a><br>
<br></blockquote></div><br></div>