QA/Automation/Meetings/120625: Difference between revisions
< QA | Automation | Meetings
Jump to navigation
Jump to search
| Line 52: | Line 52: | ||
== Infrastructure == | == Infrastructure == | ||
* | * Waiting for ESX VM templates. | ||
== Mozmill == | == Mozmill == | ||
Revision as of 18:11, 25 June 2012
previous meeting | Meetings | next meeting »
Dial in
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=PGtLpx3XQGJz # Phone: 650-903-0800 or 650-215-1282 x92 Conf# 9654 (US/INTL) # 1-800-707-2533 (pin 369) Conf# 9654 (US) # IRC: irc://irc.mozilla.org:6697/#automation
General
- Attendees:
- TBD
- This meeting:
- Chair: Dave Hunt
- Notes: Henrik Skupin
Last Weeks Action Items
- [DONE] Henrik: Check if log() method is still broken.
- This works fine in tests but I have another proposal. See below in roundtable.
- [CARRY OVER] Clint: Create templates for all the VMs.
- [DONE] Henrik: Update wiki with details of Mac OS X 10.8 media and destination hardware location.
- [ON TRACK] Henrik: Fix the Automation Developer/Development discrepancies on the wiki.
- [DONE] Henrik: Raise QA training sessions for Mozmill test development in QA staff meeting.
Roundtable
- Some questions about enhancements for Mozmill 2:
- Shall we enable pprint-color for Mozmill CLI by default? This would help all of our contributors in running tests and reporting brokenness. Automation tools whould make use of the --console-level option and select json.
- What should we define as test report? Right now we send pass/fail on each single test, even for clicks, keypresses and others. Shall we change this to expect/assert calls only? Do we want to report passed clicks as info entries? That way we can make the test module result a 'Test End' event and report the timing instead of the pass/failure - similar to Mochitest.
Q2 2012 Goals Overview
Please mark topics which need to be discussed in the meeting as bold
Issues / Blockers
- No updates
Mozmill 2.0
- Fixed a couple of issues for user restart tests - only one or two known issues are remaining
- Started refactoring of Mozmill Python code to make it easier to use the API
- Changed the way how we log entries to the console. Check this out it looks awesome especially with pprint-color!
- Mutt has been changed so JS tests don't get run in isolation mode by default. That caused us some regressions Mutt hasn't reported
- All files in the Mozmill repository are PEP8 conform now!
Mozmill 2.0 support for Automation Scripts
- No updates
Mozmill Tests API refactor
- No updates
Project Updates
Please mark topics which need to be discussed in the meeting as bold
Infrastructure
- Waiting for ESX VM templates.
Mozmill
Automation
- No updates
Dashboard
- No updates
- No updates
Selenium
- No updates
Add-ons
- No updates
Personal Status
For the personal status please check the weekly status updates:
Meeting Notes
The meeting notes for this meeting can be read in the following etherpad:
Action items
- [NEW] %name%: %task%