<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 6, 2013 at 10:42 AM, Carol Sanders <span dir="ltr"><<a href="mailto:carol@carolsanders.org" target="_blank">carol@carolsanders.org</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"><div><div><div>I would like to help fix Jenkins jobs if the task hasn't been taken. I'm just starting to implement Jenkins at work so this would help my learning curve.<br>
</div></div></div></div></blockquote><div><br></div><div style>Hi Carol, </div><div style><br></div><div style>One of the things that makes browser testing/UI testing unusual is that unlike unit tests, UI tests can fail for all sorts of reasons. Analyzing test failures is interesting and sometimes challenging work. </div>
<div style><br></div><div style>We recently made some major changes to how we do builds, and we're just now sorting some of the technical debt from that move, so the timing is good for this sort of thing. </div><div style>
<br></div><div style>To get started, take a look at <a href="https://wmf.ci.cloudbees.com/">https://wmf.ci.cloudbees.com/</a></div><div style><br></div><div style>You'll see that our builds are arranged according to target test environment and browser. You'll see that most of the Firefox/Chrome builds are (usually) green, and a number of IE builds are (usually) red. </div>
<div style><br></div><div style>To diagnose a failed build, do this: </div><div style><br></div><div style>* Find a red build at <a href="https://wmf.ci.cloudbees.com/">https://wmf.ci.cloudbees.com/</a> and click it in Jenkins</div>
<div style>* Click "Latest test result" where it shows at least one failure<br></div><div style>* Clck whatever "Test Name" interests you under "All failed tests"</div><div style>* This is a critical page, pay close attention to the "Message" section at the bottom of the page, this is the test framework saying what went wrong with the test run.<br>
</div><div style>* With the failure message in mind, click to the Sauce Labs page. </div><div style>* On the Sauce Labs page you can find a video of the test run and screen shots taken throughout the course of the test run. These are often valuable when figuring out what went wrong in a particular test. </div>
<div style><br></div><div style>Some common modes of failure: </div><div style><br></div><div style>* Some page element is visible but should not be</div><div style>* Some page element is not visible but should be</div><div style>
* The test times out waiting for some condition</div><div style>* Some system error occurs</div><div style><br></div><div style>If the test failure indicates a bug, discussing it here is a great idea. Then we can file an issue in Bugzilla using the "browser-test-bug" keyword, for example like <a href="https://bugzilla.wikimedia.org/show_bug.cgi?id=47837">https://bugzilla.wikimedia.org/show_bug.cgi?id=47837</a></div>
<div style><br></div><div style>Keeping the builds green for IE is a challenge because the Selenium Webdriver "IEDriver" is less robust than the drivers for Firefox, Chrome, and Opera. IEDriver gets significantly less attention than the other browser drivers, and is quite a bit flakier. In particular, we find that our UploadWizard application tends to work reasonable well in IE for real users, but automated tests don't work particularly well, and we suspect that IEDriver is the culprit. </div>
<div style><br></div><div style>-Chris </div><div style> </div><div><br></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><div><div><br></div>I open to any method of collaboration: IRC/Skype/Google Hangout.<br>
</div>I would prefer as a first time to 'hangout' with someone more experienced in this environment as not to make more work for fellow helpers.<br><br></div>Thanks,<br><br>Carol<br></div><div class="gmail_extra">
<br clear="all"><div><span style="background-color:rgb(0,0,0)"><font color="#cc33cc">Carol A. Sanders</font><br><font color="#009900">Sr, Network QA Engineer, Mad Scientist, Student</font><br><font>"<font color="#ffccff">Escape</font> <font color="#33cc00">the Boundaries of</font> <font color="#ff0000">Your Mentality</font>"</font></span></div>
<br><br><div class="gmail_quote"><div><div class="h5">On Tue, Jun 4, 2013 at 10:46 AM, Željko Filipin <span dir="ltr"><<a href="mailto:zfilipin@wikimedia.org" target="_blank">zfilipin@wikimedia.org</a>></span> wrote:<br>
</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><div class="h5">
<div dir="ltr">Hi everybody,<br><br>a few people said they would like to contribute. I guess some of you already know how you would like to contribute, like helping organising event(s).<br><br>I know that at least a few of you need a bit of guidance for the first few contributions, because you have told me so. :) Chris has already sent a few posts saying how you could get involved. I have a few smaller and more focused tasks that could be a good way for somebody to get involved.<br>
<br>You can do all tasks on your own time, or we could arrange a pairing session on IRC/Skype/Google Hangout. Tasks are sorted roughly by how hard they are.<br><br>#1 fix class name<br><br>visual_editor_page.rb[1] file has wrong class name, UserPage. It should be VisualEditorPage. The task is to rename the class. It should be trivial to do. Depending on your Git and/or Github/Gerrit skills, submitting the code would probably be harder than fixing it.<div>
<br></div><div><div>#2 fix failing Jenkins job(s) for desktop browsers</div><div><br></div><div>Chris and I are doing our best to keep Jenkins jobs running tests on desktop browsers[2] green, but things change a lot and the tests start failing. Additionally, we recently made a few significant changes to Jenkins jobs (targeting more environments) and a lot of tests are failing at the moment. If you would to help us fix a test/job (or six), let me know. Sometimes the fix is as simple as disabling a test that fails because it by mistake tries to test a feature that is not enabled at certain environment. As with task #1 the fix is trivial, and the harder part would probably be submitting code to Github/Gerrit.</div>
</div><div><br></div><div>#3 fix failing Jenkins job(s) for mobile browsers</div><div><br></div><div>All Jenkins jobs running tests for mobile browsers[3] are disabled because they started failing and nobody had the time to investigate and fix the problems. If you are interested in testing on mobile browsers and/or devices, this is a task for you. I can help you pick and fix at least one test.</div>
<div><br></div><div><br></div><div>Regarding tasks #2 and #3: I feels great to fix a broken build and to see a job going from red to green. Trust me.</div><div><br></div><div><div>Željko</div><div>
--</div><div>1: <a href="https://github.com/wikimedia/qa-browsertests/blob/master/features/support/pages/visual_editor_page.rb#L1" target="_blank">https://github.com/wikimedia/qa-browsertests/blob/master/features/support/pages/visual_editor_page.rb#L1</a></div>
</div><div>2: <a href="https://wmf.ci.cloudbees.com/view/r-bt/" target="_blank">https://wmf.ci.cloudbees.com/view/r-bt/</a></div><div>3: <a href="https://wmf.ci.cloudbees.com/view/r-mf/" target="_blank">https://wmf.ci.cloudbees.com/view/r-mf/</a><br>
</div></div>
<br></div></div>_______________________________________________<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></blockquote></div><br></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>