Web Testing/Automation/automation-14-10-2011: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 2: | Line 2: | ||
== Action Items from last meeting == | == Action Items from last meeting == | ||
* Stephen to file an IT bug to open up port 8080 once we've integrated LDAP | * Stephen to file an IT bug to open up port 8080 once we've integrated LDAP | ||
** DONE! | ** DONE! {{bug|693544}} | ||
* Set up a Firefox 7 environment on Selenium Grid | * Set up a Firefox 7 environment on Selenium Grid | ||
** DONE! | ** DONE! | ||
| Line 52: | Line 52: | ||
== Action Items == | == Action Items == | ||
* Stephen | * Stephen: Follow-up with Gerv on licensing issues with our tests. | ||
* Add Firefox variable for versions to the global variables in Jenkins and use it | * Add Firefox variable for versions to the global variables in Jenkins and use it. | ||
** Suggest FIREFOX_VERSION | |||
* All project owners: Standardise on a requirements.txt in the top level of your project's repository. | |||
* Dave: Submit a pull request for Input to move the tests into a top level tests directory. | |||
* Marlena: Configure a job in Jenkins to limited archived builds and report the results (are top level graphs unaffected). | |||
* Zac: Merge branch with Selenium 2.8.0 to master on moz-grid-config and update all nodes to use the latest from master. | |||
Latest revision as of 16:51, 14 October 2011
<< Last meeting | WebQA Automation | Next meeting >>
Action Items from last meeting
- Stephen to file an IT bug to open up port 8080 once we've integrated LDAP
- DONE! bug 693544
- Set up a Firefox 7 environment on Selenium Grid
- DONE!
Discussion topics / General Updates
- Dave Dash has suggested an alternative to including MPL in every file in our test repositories.
- New page object organisation being used on Input. What do people think?
- This is really trivial but would be great to standardise on our pip requirements files. Variations are:
- requirements/mozwebqa.txt
- requirements/requirements.txt
- requirements.txt
- How many builds do we really need to archive? https://bugzilla.mozilla.org/show_bug.cgi?id=693544#c5
- Dave Hunt's idea for simplifying job configuration in Jenkins
Status Update
AMO [CI]
- Fixing failed tests for themes and search
- work continues on testing payments
Flightdeck/Addon-Builder [CI]
- Some issue with staging failures which seems to be related to performance. More investigation required.
- FD on jenkins can't clean up its own data because urllib requests hit some kind of proxy issue.
SUMO [CI]
Input [CI]
- Dave Hunt restructured Input with https://github.com/mozilla/input-tests/pull/96
Socorro [CI]
- Socorro needs merge attention - https://github.com/mozilla/Socorro-Tests/pulls
- Team RO has been quite involved with pull requests and has been actively merging code. Woot!
MDN [CI]
Mozilla.com [CI]
QMO [CI]
Wiki [CI]
Action Items
- Stephen: Follow-up with Gerv on licensing issues with our tests.
- Add Firefox variable for versions to the global variables in Jenkins and use it.
- Suggest FIREFOX_VERSION
- All project owners: Standardise on a requirements.txt in the top level of your project's repository.
- Dave: Submit a pull request for Input to move the tests into a top level tests directory.
- Marlena: Configure a job in Jenkins to limited archived builds and report the results (are top level graphs unaffected).
- Zac: Merge branch with Selenium 2.8.0 to master on moz-grid-config and update all nodes to use the latest from master.