46
edits
QA/Execution/Web Testing/Meetings/2012-05-31: Difference between revisions
QA/Execution/Web Testing/Meetings/2012-05-31 (view source)
Revision as of 18:56, 6 June 2012
, 6 June 2012→Action Items / Takeaways
Ajalgaonkar (talk | contribs) |
|||
| (13 intermediate revisions by 5 users not shown) | |||
| Line 3: | Line 3: | ||
= Meeting Details = | = Meeting Details = | ||
{{:QA/Execution/Web Testing/Meetings}} | {{:QA/Execution/Web Testing/Meetings}} | ||
= Discussion Items / Updates = | = Discussion Items / Updates = | ||
| Line 24: | Line 20: | ||
* Stalled builds are back, and now we have the backup plugin there's a new side-effect: the plugin prepares Jenkins for shutdown before a backup, but waits for all jobs to complete (and enforces 'quiet node' after waiting 2 hours). If there are stalled jobs then Jenkins is essentially doing nothing until the jobs are aborted. I think we may need to investigate using the [http://pypi.python.org/pypi/pytest-timeout pytest-timeout] plugin, however it currently clashes with pytest-mozwebqa. For now I have re-enabled abort for amo.dev and marketplace.dev. | * Stalled builds are back, and now we have the backup plugin there's a new side-effect: the plugin prepares Jenkins for shutdown before a backup, but waits for all jobs to complete (and enforces 'quiet node' after waiting 2 hours). If there are stalled jobs then Jenkins is essentially doing nothing until the jobs are aborted. I think we may need to investigate using the [http://pypi.python.org/pypi/pytest-timeout pytest-timeout] plugin, however it currently clashes with pytest-mozwebqa. For now I have re-enabled abort for amo.dev and marketplace.dev. | ||
* After investigating the above, I noticed that the backups were failing. This was due to the drive they are backed up to not being mounted. I have fixed this, but it should be a buildmaster responsibility to ensure backups are successful. | * After investigating the above, I noticed that the backups were failing. This was due to the drive they are backed up to not being mounted. I have fixed this, but it should be a buildmaster responsibility to ensure backups are successful. | ||
* There seems to still be confusion over implicit/explicit timeouts with WebDriver and Selenium Grid timeouts. The former are important to understand when writing tests. How can we improve this situation? | * There seems to still be confusion over implicit/explicit timeouts with WebDriver and Selenium Grid timeouts. The former are important to understand when writing tests. How can we improve this situation? [https://wiki.mozilla.org/QA/Execution/Web_Testing/Docs/Automation/Testcases/Guidelines#Actions implicit & explicit wait] | ||
* We still need (per our Q2 goals) 3 testdays -- what's yours going to be on, and when? :-) | * We still need (per our Q2 goals) 3 testdays -- what's yours going to be on, and when? :-) | ||
** Remember, they don't have to be on Friday... | ** Remember, they don't have to be on Friday... | ||
* | * Devices update: | ||
** Softvision should be able to get what they need, per Bob | ** Softvision should be able to get what they need, per Bob | ||
** for the rest of us: guideline is "as many devices as the team reasonably needs" | ** for the rest of us: guideline is "as many devices as the team reasonably needs" | ||
| Line 34: | Line 30: | ||
**** just run on Samsung Nexus S | **** just run on Samsung Nexus S | ||
* How are we doing with investigating performance testing/tools/metrics we need to measure? | * How are we doing with investigating performance testing/tools/metrics we need to measure? | ||
= Engagement Project Status = | = Engagement Project Status = | ||
| Line 52: | Line 47: | ||
*Mozilla.com | *Mozilla.com | ||
** pushing this weeks release today | |||
*Mozillians | *Mozillians | ||
| Line 61: | Line 57: | ||
*** the tree is open for commits - the 06-06-2012 train leaves this morning | *** the tree is open for commits - the 06-06-2012 train leaves this morning | ||
*MDN | *MDN | ||
** pushed on [http://scrumbu.gs/projects/mdn/ Tuesday] | |||
*Socorro | *Socorro | ||
| Line 73: | Line 70: | ||
= Buildmaster = | = Buildmaster = | ||
* Rebecca is next | |||
= Community Update = | = Community Update = | ||
* https://wiki.mozilla.org/QA/QA_Community/Meetings/2012-05-30 | |||
= Time off / Out-of-office = | = Time off / Out-of-office = | ||
| Line 80: | Line 79: | ||
* davehunt: 06/04 - 06/05 Public holiday in the UK | * davehunt: 06/04 - 06/05 Public holiday in the UK | ||
* davehunt: 06/06 - 06/13 PTO | * davehunt: 06/06 - 06/13 PTO | ||
* June 4th is a national holiday in Romania - TeamRO will be out of office | |||
= Action Items / Takeaways = | |||
* Takeaways: | |||
Dave's Clarification on | |||
Selenium issues discussion: | |||
** Implicit things that are introduced into new selenium, time out and timing the tests. | |||
** Time out related to py.tests. | |||
** Implicit wait times are hard coded | |||
** Time out and implicit time out are they the same. | |||
Talk to stephen about test dates and if available for one. | |||
Device situation in WebQA team: | |||
every one who wants to get a B2G phone, Consult with Stephen and have to talk with Clint | |||
Tagret phones going to be introduced in a few weeks. Currently supports Galaxy S2 and Google Nexus. | |||
SLA still being worked on | |||
* Action Items: | * Action Items: | ||
** | **Remind Stephen about 2.22 problem talked about in the meeting to get it back up and working | ||
* | **Raymond and Stephen: Talk with Clint about Mobile phones test (B2G) | ||
* | **Stephen & Krupa: needs to talk to Jason about top app testing | ||
**Krupa: to talk about new new tab next week. | |||
**Stephen: To see the best way to get status updates on marionette on B2G. | |||
**Stephen: Talk to Jake from IT for performance monitoring. | |||
**Rebecca: to ask Dev's how project affected by K9o. | |||
* Next owner: Aditya | |||