QA/Execution/Web Testing/Meetings/2012-03-01: Difference between revisions
< QA | Execution | Web Testing | Meetings
Jump to navigation
Jump to search
Teodosia.pop (talk | contribs) |
|||
| Line 20: | Line 20: | ||
** Who's the target audience, besides Webdev and WebQA? | ** Who's the target audience, besides Webdev and WebQA? | ||
* Can we delete http://qa-selenium.mv.mozilla.com:8080/job/apps.preview.dev/ ? | * Can we delete http://qa-selenium.mv.mozilla.com:8080/job/apps.preview.dev/ ? | ||
* Goals! | |||
** https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2012/Q1 | |||
*** How are we doing? Any blockers? | |||
= Engagement Project Status = | = Engagement Project Status = | ||
Revision as of 16:54, 1 March 2012
previous mtg | Web QA Home | next mtg
Meeting Details
Please see our public calendar for all upcoming events and meetings.
Our regular team meeting occurs every Thursday @ 9am Pacific
Action Items / Takeaways from Last Week
- Note: All previous meeting's action items were about work week so I removed them
Discussion Items / Updates
- We won't upgrade grid to 2.20.0, we will wait for 2.21.0 which will include bug fixes that promise to fix our timeout issues.
- Dave and Zac discussed Jenkins job changes and that led us to this plugin which saves previous configurations. For now it will be useful for us but we want to extend it further to include a save message (like a commit message on Git) for communication. https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin
- Audit of existing plugins on Jenkins - can we remove any that are unused?
- WebQA blog - when will it be ready? I (Zac) have a blog ready for it.
- It's an IT bug away -- has it been filed yet?
- pytest-mozwebqa 0.9 (possibly) ready for testing with production testing safeguards.
- Do we have/want to have a policy regarding import order, from PEP8?
- PEP8 already has one, and we're PEP8 compliant so... do we need to call it out explicitly?
- I'm not picking on SUMO, but looks like we do? See, e.g., https://github.com/mozilla/sumo-tests/blob/master/tests/desktop/test_article_create_edit_delete.py
- PEP8 already has one, and we're PEP8 compliant so... do we need to call it out explicitly?
- We need to promote automation when it finds bugs. What do we currently do with [fromAutomation] whiteboard entries and how can we make these more visible?
- Who's the target audience, besides Webdev and WebQA?
- Can we delete http://qa-selenium.mv.mozilla.com:8080/job/apps.preview.dev/ ?
- Goals!
- https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2012/Q1
- How are we doing? Any blockers?
- https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2012/Q1
Engagement Project Status
If you've worked on an engagement project in the last week, enter your name, the project name, and time spent in hours (estimated).
- DTPT Phase II - Worked on bug verification, project is waiting for a security review. Estimate: 1 hr
- Betafarm - Introductory meeting & ramp up. Estimate: 2 hrs
- Firefox Flicks
- Stephen; estimate: 6+ hours
Project Status / goals for next week (keep it brief)
- Affiliates
- Successful 2.22.12 release
- no release this week - Flux team is having a workweek
- AMO
- Marketplace
- Input
- Jetpack Builder (aka FlightDeck)
- Mozilla.com
- Mozillians
- Feature testing is currently blocked by bug 731206
- We have 2 new contributors on the project. One WebDev and one QA.
- MDN
- Socorro
- 2.4.4 milestone released on 2/29
- May do an out of band release to land ESR support
- Automation caught a serious regression on production spurring a 2nd release - bug 731785
- SUMO
- Case Conductor
- .8 release in progress, testing locally, waiting for IT to get allizom.org site up
Community Update
Time off / Out-of-office
- Zac 5th March 2012 (1 day)
- Teodosia 2nd March until 9th March (6 days)
Takeaways and Action Items
- Takeways:
- Action Items:
- Next owner:
- Next week's meeting notes: