canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,747
edits
QA/Test Automation/2011-06-01: Difference between revisions
→Meeting Notes
| Line 98: | Line 98: | ||
= Meeting Notes = | = Meeting Notes = | ||
* Review Process | |||
** WebQA [https://wiki.mozilla.org/Web_Testing/Automation/CodeReviewProcess Review Process] that we can use to start | |||
* Tests for the Discovery Pane | |||
** Currently there are [https://github.com/mozilla/Addon-Tests/blob/master/test_discovery_page.py 13 selenium tests] for discovery pane | |||
** In Mozmill tests we should only test what cannot be done with Selenium | |||
*** Download and installation of Add-ons including behavioral changes of sections | |||
*** General interaction with the browser | |||
** What process do we need to become faster | |||
*** Before starting to write a test get in contact with David or Krupa and figure out which parts of a Litmus test do not need coverage and can be skipped | |||
==Action items== | ==Action items== | ||
* Geo: Send pivotaltracker | * Geo: Send pivotaltracker project link for API refactoring project to team members or add it to the project wiki | ||
* David | * David: Work with Geo and Anthony to get some first ideas for changes of the review process; we will schedule a meeting once Henrik is back (should happen in June) | ||
* Anthony: | * Anthony: Touch base with Geo to fix on-demand daemon issue | ||
* Anthony: Review patch from Henrik tonight for remote tests | |||
* | * Anthony: Move SSL tests over to mozqa.com once Al put them up on mozqa.com | ||
* | * Anthony: Send email today to Dave Burns, Krupa, Vlad, Alex, Henrik to identify unnecessary tests inside a Litmus test which we have already started to automate. We need this information ASAP. Also make it clear how to handle new tests. | ||
* | * Henrik: Create necessary dummy patches for remote test-run | ||
* | * Henrik: Send Cameron the contacts from LibreOffice | ||