<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 15, 2013 at 6:43 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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Let's hear it :)</div></blockquote><div>
<br></div><div>Here goes... </div><div><br></div><div>There is a certain tension in the testing community between advocates for UI/browser test automation and advocates for human "sapient" testing. I'd like to go there. </div>
<div><br></div><div>Specifically, I'd like to do this with Weekend Testing: </div><div><br></div><div>* Pick a complex feature for which browser test automation exists. Right now I'm thinking CirrusSearch or VisualEditor. Because we're using Cucumber, the test Scenarios should be understandable by people who are not programmers. Because we're using the page_object Ruby gem, the guts of the tests should be readable by people with programming experience in just about any language. Regardless of level of expertise, we should be able to provide everyone a local test environment from which to run the automated tests against WMF hosts either natively or with a VirtualBox VM configured via vagrant (<a href="http://www.mediawiki.org/wiki/Vagrant">http://www.mediawiki.org/wiki/Vagrant</a>). We have done this before: </div>
<div><br></div><div>online: <a href="https://www.mediawiki.org/wiki/Meetings/2013-07-18">https://www.mediawiki.org/wiki/Meetings/2013-07-18</a><br></div><div>live: <a href="https://www.mediawiki.org/wiki/Meetings/2013-06-27">https://www.mediawiki.org/wiki/Meetings/2013-06-27</a></div>
<div><br></div><div>Given a robust set of automated browser tests and the ability to run them, let us then: </div><div><br></div><div>* Identify deficiencies in the automated test coverage for the feature. This may or may not include analysis of the test code itself, but would certainly at least include analysis of the ATDD-style stated feature coverage in the Cucumber Scenarios. Do we have any technical debt in our test code?</div>
<div><br></div><div>* Identify test charters for which automated testing is not possible and which are only testable by actual human beings. Are there tests that cannot be automated, and is such testing worthwhile? </div>
<div><br></div><div>Outcomes: </div><div><br></div><div>* Participants will be able to analyze ATDD-style automated browser tests</div><div>* Participants will be able to run Cucumber + page_object browser tests and analyze the results of those tests</div>
<div>* Participants will be able to demonstrate automated browser test practices with examples from the open WMF browser test code</div><div>* Participants will be able to begin to contribute to WMF testing efforts if they wish, whether automated or not</div>
<div><br></div><div>This might be too ambitious. I'm pretty sure this would be the most technically challenging session in the history of WTA. OTOH, we've already built the infrastructure to do this kind of thing, let's spread the word about what is possible. </div>
<div><br></div><div>-Chris </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
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."<div class="im"><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: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"<div class="im"><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></div></blockquote></div>
</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></div>