|
|
| Line 86: |
Line 86: |
| = 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 ==
| |
|
| |
| == Wednesday's Notes ==
| |
|
| |
| [[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
| |
|
| |
| == Thursday's Notes ==
| |
|
| |
| [[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.
| |
| *Use Pivitol Tracker
| |
| *Stephen to talk to Dave Dash and see about co-developing a fuzzing tool a la PowerFuzzer
| |
|
| |
| === 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
| |
|
| |
| == Friday's Notes<br> ==
| |
|
| |
| [[https://docs.google.com/document/d/1c4Rk4DjoTUjnUUBhRnNfUQqOWZezHcequm6lVXXgX6Q/edit?hl=en_US full meeting minutes]]
| |
| === 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
| |
| *Nightly, Aurora, Beta, RC FF
| |
| **need to explore an automated way to upgrade Nightly & Aurora
| |
| **doing this cleanly would be a nice contribution to the community
| |
| **Ensure Se supports Nightly & Aurora envs
| |
| *Latest Chrome, Safari (limited/non-existent Selenium support at present), Opera (you’re welcome Esteban)
| |
| *Linux, OSX, Win XP, Vista?,Win 7
| |
| *Consider Android, iPad, iPhone envs
| |
| *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
| |
| *What about Mac OS X Lion support? Do we want to maintain dual environments?
| |
| **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
| |