Confirmed users
1,867
edits
(10 intermediate revisions by the same user not shown) | |||
Line 33: | Line 33: | ||
= Agenda = | = Agenda = | ||
{| style="width: 939px; height: 139px; | {| class="fullwidth-table" style="width: 939px; height: 139px;" | ||
|- | |- | ||
| style="background: rgb(239, 239, 239); width: 25%; font-weight: bold" | Schedule | | style="background: rgb(239, 239, 239); width: 25%; font-weight: bold" | Schedule | ||
Line 45: | Line 45: | ||
| Tuesday, 10-11am & 1:30-2:30pm<br> | | Tuesday, 10-11am & 1:30-2:30pm<br> | ||
| Sessions | | Sessions | ||
| [[#Tuesday| | | [[#Tuesday|topics'''<br>''']] | ||
|- valign="top" | |- valign="top" | ||
| Wednsday, 10-12am<br> | | Wednsday, 10-12am<br> | ||
Line 79: | Line 79: | ||
*10am - 11am: Git - use, misuse, and process | *10am - 11am: Git - use, misuse, and process | ||
*11:00am - 11:30am: Gamr talk hosted by David | *11:00am - 11:30am: Gamr talk hosted by David | ||
*11:30am - 12pm: Dave Hunt's Helicopter talk | *11:30am - 12pm: Dave Hunt's Helicopter talk | ||
Line 89: | Line 89: | ||
= Action Items = | = Action Items = | ||
Items that the group felt would merit followup on | Items that the group felt would merit followup on | ||
== Tuesday's Notes == | == Tuesday's Notes == | ||
uTest | |||
[[https://docs.google.com/document/d/1iRjaQlm24khgPoAJpSMifCTae0Fd2-524DGWcVODSOA/edit?hl=en_US full meeting minutes]] | |||
=== uTest === | |||
*Krupa, Rebecca, and Matt to work on getting a checklist for uTest projects things we need their testers to adhere to, and whether they file directly in Bugzilla, etc. | *Krupa, Rebecca, and Matt to work on getting a checklist for uTest projects things we need their testers to adhere to, and whether they file directly in Bugzilla, etc. | ||
Waverly | |||
=== Waverly === | |||
*Assign one tester to: | *Assign one tester to: | ||
**AMO | **AMO | ||
**Socorro | **Socorro | ||
*Process outline for utilizing Waverly | *Process outline for utilizing Waverly | ||
**daily standups | **daily standups | ||
**Office hours | **Office hours | ||
**Point them to the Guidelines | **Point them to the Guidelines | ||
Line 104: | Line 110: | ||
*Team to try using GitHub issues, talk to someone who’s using it | *Team to try using GitHub issues, talk to someone who’s using it | ||
**Raymond said to ask Dietrich | **Raymond said to ask Dietrich | ||
== Wednesday's Notes == | |||
*Stephen to talk to Justin Lazarao about the load-testing cluster | == Wednesday's Notes == | ||
*Stephen to talk to James Bonacci | |||
*Investigate multi-node JMeter? | [[https://docs.google.com/document/d/1xIp1-6ix6pi4EayOC1eZ-j8ShyqNHj2_nwdrUyK8J4E/edit?hl=en_US full meeting minutes]] | ||
=== Load Testing === | |||
*Stephen to talk to Justin Lazarao about the load-testing cluster | |||
*Stephen to talk to James Bonacci | |||
*Investigate multi-node JMeter? | |||
*Can trigger JMeter from a simple ant script in CI | *Can trigger JMeter from a simple ant script in CI | ||
== Thursday's Notes == | == Thursday's Notes == | ||
=== Git === | |||
*Stephen & Matt B. to create a visual diagram of the git clone/branch/merge/review process. | [[https://docs.google.com/document/d/1wDq70o6bmDWOcLFZoD1J7BWsw5rmls9mM3InNHCqtW8/edit?hl=en_US full meeting minutes]] | ||
=== Git === | |||
*Stephen & Matt B. to create a visual diagram of the git clone/branch/merge/review process. | |||
*Team members can consider sitting through test reviews with one another to learn from one another. | *Team members can consider sitting through test reviews with one another to learn from one another. | ||
*Use Pivitol Tracker | *Use Pivitol Tracker | ||
*Stephen to talk to Dave Dash and see about co-developing a fuzzing tool a la PowerFuzzer | *Stephen to talk to Dave Dash and see about co-developing a fuzzing tool a la PowerFuzzer | ||
=== Garmr === | |||
*pip installable | === Garmr === | ||
*https://github.com/AutomatedTester/Garmr | |||
*pip installable | |||
*https://github.com/AutomatedTester/Garmr | |||
*meant to check security items on our security check list - https://wiki.mozilla.org/WebAppSec/Secure_Coding_QA_Checklist | *meant to check security items on our security check list - https://wiki.mozilla.org/WebAppSec/Secure_Coding_QA_Checklist | ||
== Friday == | |||
*remove the blocker dependency, get Se2 running | == Friday's Notes<br> == | ||
*finding a project that we can try out BrowserMob with, and do a trial run | |||
*Need a real strategy for the environments that we need to support | [[https://docs.google.com/document/d/1c4Rk4DjoTUjnUUBhRnNfUQqOWZezHcequm6lVXXgX6Q/edit?hl=en_US full meeting minutes]] | ||
**we should be using Webtrends+anticipated users’ platforms (we want to support other platforms for conversion) | === Our Automation Env === | ||
*remove the blocker dependency, get Se2 running | |||
*finding a project that we can try out BrowserMob with, and do a trial run | |||
*Need a real strategy for the environments that we need to support | |||
**we should be using Webtrends+anticipated users’ platforms (we want to support other platforms for conversion) | |||
*Grid 2 is again a dependency/blocker | *Grid 2 is again a dependency/blocker | ||
*Nightly, Aurora, Beta, RC FF | *Nightly, Aurora, Beta, RC FF | ||
**need to explore an automated way to upgrade Nightly & Aurora | **need to explore an automated way to upgrade Nightly & Aurora | ||
**doing this cleanly would be a nice contribution to the community | **doing this cleanly would be a nice contribution to the community | ||
**Ensure Se supports Nightly & Aurora envs | **Ensure Se supports Nightly & Aurora envs | ||
*Latest Chrome, Safari (limited/non-existent Selenium support at present), Opera (you’re welcome Esteban) | *Latest Chrome, Safari (limited/non-existent Selenium support at present), Opera (you’re welcome Esteban) | ||
*Linux, OSX, Win XP, Vista?,Win 7 | *Linux, OSX, Win XP, Vista?,Win 7 | ||
*Consider Android, iPad, iPhone envs | *Consider Android, iPad, iPhone envs | ||
*explore targeting specific platforms with Se (Firefox x on Windows x, etc.) -- granularity with environments for test runs | *explore targeting specific platforms with Se (Firefox x on Windows x, etc.) -- granularity with environments for test runs | ||
*Look at resurrecting an Ubuntu Linux environment for Selenium | *Look at resurrecting an Ubuntu Linux environment for Selenium | ||
*What about Mac OS X Lion support? | *What about Mac OS X Lion support? Do we want to maintain dual environments? | ||
**Which testruns run in Snow Leopard, which run in Lion? | **Which testruns run in Snow Leopard, which run in Lion? Do we want a blend of both? | ||
**Modify the current environment string to differentiate between the two versions | **Modify the current environment string to differentiate between the two versions |