Web Testing/Automation/automation-22-07-2011: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[[Web_Testing/Automation/automation-01-07-2011| << Last meeting]] | [https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation WebQA Automation] | [[Web_Testing/Automation/automation-22-07-2011| Next meeting >>]]
[[Web_Testing/Automation/automation-01-07-2011| << Last meeting]] | [https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation WebQA Automation] | [[Web_Testing/Automation/automation-05-08-2011| Next meeting >>]]
== Discussion topics ==
== Discussion topics ==
* Any progress on using py.test marks unambiguously?
* Any progress on using py.test marks unambiguously?
* a/b testing
* a/b testing
* CI job name convention
* CI job name convention; suggestion:
** amo.zamboni.allizom.bft
* Leadership of the meetings/timing of the wiki page being sent out
* Leadership of the meetings/timing of the wiki page being sent out
* Need a meeting to discuss sharing Waverly resources between WebQA projects and how that will be communicated
* Need a meeting to discuss sharing Waverly resources between WebQA projects and how that will be communicated
Line 17: Line 18:


=== [https://wiki.mozilla.org/Sumo SUMO] [[http://qa-selenium.mv.mozilla.com:8080/view/SUMO%20Tests/ CI]] ===
=== [https://wiki.mozilla.org/Sumo SUMO] [[http://qa-selenium.mv.mozilla.com:8080/view/SUMO%20Tests/ CI]] ===
*  
* fixed [https://github.com/mozilla/sumo-tests/pull/14 test_questiosn_sort.py]


=== [https://wiki.mozilla.org/Firefox/Input Input] [[http://qa-selenium.mv.mozilla.com:8080/job/input%20stage/ CI]] ===
=== [https://wiki.mozilla.org/Firefox/Input Input] [[http://qa-selenium.mv.mozilla.com:8080/job/input%20stage/ CI]] ===
Line 36: Line 37:


=== [https://wiki.mozilla.org/QA/Execution/Web_Testing/Wiki_Test_Coverage Wiki] [[http://qa-selenium.mv.mozilla.com:8080/job/wiki.prod/ CI]] ===
=== [https://wiki.mozilla.org/QA/Execution/Web_Testing/Wiki_Test_Coverage Wiki] [[http://qa-selenium.mv.mozilla.com:8080/job/wiki.prod/ CI]] ===
*  
* Tests are occasionally failing due to Selenium bug [http://code.google.com/p/selenium/issues/detail?id=1020 1020]
* Tests are also sometimes failing due to page title being blank. David Burns is investigating. May be a Selenium issue.


== Action Items ==
== Action Items ==
*
* Post Waverly visit conversation with team
* Get an update from David regarding py.test decorators
* Meeting owners should send out the an email 24-hours prior to the meeting with an url to the wiki to give people time to insert updates and discussion items.
 
== Next Meeting Owner/Chair ==
* Krupa

Latest revision as of 16:41, 22 July 2011

<< Last meeting | WebQA Automation | Next meeting >>

Discussion topics

  • Any progress on using py.test marks unambiguously?
  • a/b testing
  • CI job name convention; suggestion:
    • amo.zamboni.allizom.bft
  • Leadership of the meetings/timing of the wiki page being sent out
  • Need a meeting to discuss sharing Waverly resources between WebQA projects and how that will be communicated

Status Update

AMO [CI]

  • Getting closer to handling impala vs. zamboni
    • Still need a better long term solution for a/b testing Marlena will talk to AMO devs about this
  • Stand ups are working
  • code review queue slowly getting processed

SUMO [CI]

Input [CI]

  • Working with Webdev to diagnose the timeouts on stage (tofumatt ftw)

Socorro [CI]

  • Elastic Search should land soon (today or early next week). Once it does going to rev. up a Waverly resource.

MDN [CI]

Mozilla.com [CI]

QMO [CI]

  • CAPTCHA removed from staging to allow tests to run.
  • Outstanding PHP issue still being investiated. bug 667495

Wiki [CI]

  • Tests are occasionally failing due to Selenium bug 1020
  • Tests are also sometimes failing due to page title being blank. David Burns is investigating. May be a Selenium issue.

Action Items

  • Post Waverly visit conversation with team
  • Get an update from David regarding py.test decorators
  • Meeting owners should send out the an email 24-hours prior to the meeting with an url to the wiki to give people time to insert updates and discussion items.

Next Meeting Owner/Chair

  • Krupa