QA/Execution/Web Testing/Meetings/2015-10-22: Difference between revisions

 
(14 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Meeting details =
= Meeting details =
{{:QA/Execution/Web Testing/Meetings}}
{{:QA/Execution/Web Testing/Meetings}}
* [https://air.mozilla.org/web-qa-weekly-meeting-20150723/ Recording]
* [https://air.mozilla.org/web-qa-weekly-meeting-20151022/ Recording]


=  Lead / Scribe =
=  Lead / Scribe =
* Lead: Bob
* Lead: <strike>Bob</strike> Rebecca
* Scribe: Rebecca
* Scribe: <strike>Rebecca</strike> Stephen
** Scribe is responsible for:
** Scribe is responsible for:
*** adding the action items and takeaways to the current meeting's minutes
*** adding the action items and takeaways to the current meeting's minutes
Line 16: Line 16:
** Staging has been updated and is being tested - some issues were found - searching the suitable fix
** Staging has been updated and is being tested - some issues were found - searching the suitable fix
** Pull request to fix BIDPOM: https://github.com/mozilla/bidpom/pull/99
** Pull request to fix BIDPOM: https://github.com/mozilla/bidpom/pull/99
* [davehunt] [http://webqa-ci-staging1.qa.scl3.mozilla.com:8080/view/Dashboard/ Jenkins dashboard view]   
* {{done|}}[davehunt] [http://webqa-ci-staging1.qa.scl3.mozilla.com:8080/view/Dashboard/ Jenkins dashboard view]   
** https://webqa-ci.mozilla.com/view/Dashboard/  
** https://webqa-ci.mozilla.com/view/Dashboard/  


Line 23: Line 23:


= Discussion items =
= Discussion items =
*
* [justinpotts] (Not available to discuss with you guys, but let me know your thoughts) MozWebQA Dashboard Redesign
** I'd like to redesign the dashboard and make it a little bit cleaner and more intuitive for new contributors as well as experienced team members to use.
** Some of the ideas I have in mind are a main dashboard page for quick stats, individual pages for each repository, and two pages for issues and pull requests as well as Continuous Integration statuses.
** I have worked on some mockups for a few pages. You can view these [http://share.pho.to/9nwDE here].
** If we decide to move forward with this, I'll need to take a closer look at the back-end portion and see what is possible with what I would like to do, but I am anxious to hear your thoughts!
* [davehunt] Our staging environment currently has a hosts entry for www-dev.allizom.org
* [davehunt] Check out Bob's [https://pypi.python.org/pypi/pytest-repeat pytest-repeat] plugin!


= [https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2015/Q4 Goals Check-in] - 1st and 3rd meetings, monthly =
= [https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2015/Q4 Goals Check-in] - 1st and 3rd meetings, monthly =
Line 55: Line 61:
If you've worked on Jenkins or Selenium Grid in the last week, add the necessary info in the Wiki
If you've worked on Jenkins or Selenium Grid in the last week, add the necessary info in the Wiki
* [davehunt] Because the new Bedrock tests use pytest-decouple, I had to rename our virtual environment from <code>.env</code> to <code>.venv</code>.
* [davehunt] Because the new Bedrock tests use pytest-decouple, I had to rename our virtual environment from <code>.env</code> to <code>.venv</code>.
* [bsilverberg] Removed oneanddone.json from both Jenkins stage and prod and adjusted the jobs to deal with the absence of said file.
* [bsilverberg] Added #remora as a room to report build failures for marketplace.dev.developer_hub.saucelabs. This was at jason's request.


= Community update =
= Community update =
Line 69: Line 77:


= Action items =
= Action items =
*
* [davehunt] Look into latest Selenium (2.48) upgrade
* {{done|}}[davehunt] Remove HOSTS entry for www-dev.allizom.org on Selenium-staging nodes
* [all] Reminder to remove your dev/staging HOSTS entries for testing PHX1-exit migration


= Next Meeting =
= Next Meeting =
* Next owner / scribe:
* Next owner / scribe:
* Next week's meeting notes:
* Next week's meeting notes:
Confirmed users
9,511

edits