QA/Execution/Web Testing/Goals/2016/Q2: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(3 intermediate revisions by 3 users not shown)
Line 14: Line 14:
# Work with devs and ops to review and improve AMO's release process
# Work with devs and ops to review and improve AMO's release process
# Work on Webextensions release for 48 to ensure cross-platform coverage
# Work on Webextensions release for 48 to ensure cross-platform coverage
## Check if there are opportunities to engage with Chrome webextensions before the 48 release. Need to discuss with Amy and Dan before confirming on this.


===Stephen===
===Stephen===
# Get a Dockererized OWASP ZAP ([https://github.com/Grunny/zap-cli CLI]) instance up and running against a staged instance of one of our key sites: either AMO, Mozilla.org, or MDN, in Web QA's Jenkins, on either/both a cronjob or on-demand, as  goal
# Get a Dockererized OWASP ZAP ([https://github.com/Grunny/zap-cli CLI]) instance up and running against a staged instance of one of our key sites: either AMO, Mozilla.org, or MDN, in Web QA's Jenkins, on either/both a cronjob or on-demand, as  goal
#* Document (i.e. blogpost[s]) the goals, the process, the progress, to try to help increase awareness
#* Document (i.e. blogpost[s]) the goals, the process, the progress, to try to help increase awareness
## DONE: https://blog.mozilla.org/webqa/2016/06/28/dockerized-owasp-zap-security-scanning-in-jenkins-part-two/ & http://159.203.196.21:8080/job/docker-zap-cli/22/console


===Dave===
===Dave===
# Setup UI functional tests for the add-ons website to run against pull requests
# Set up UI functional tests for the add-ons website to run against pull requests
#* The UI functional tests currently live in https://github.com/mozilla/Addon-Tests and are run against deployed instances of the add-ons website. This deliverable will mean that UI functional tests will be run whenever a contributor submits a patch for consideration against an instance of the application including the change. This will reduce the feedback loop for failures, and will prevent regressions from being introduced.
#* The UI functional tests currently live in https://github.com/mozilla/Addon-Tests and are run against deployed instances of the add-ons website. This deliverable will mean that UI functional tests will be run whenever a contributor submits a patch for consideration against an instance of the application including the change. This will reduce the feedback loop for failures, and will prevent regressions from being introduced.


===Rebecca===
===Rebecca===
# Ramp up and own Shavar deployments
# Ramp up and own Shavar deployments
# Learn and implement Docker container for OneandDone
# Learn and implement Docker container locally, assist with One and Done Docker-ization


===Matt===
===Matt===

Latest revision as of 22:05, 28 June 2016

Web QA Q2 2016 Goals

Discussion Etherpad here: https://public.etherpad-mozilla.org/p/webqa-2016-q2-goals-brainstorm

Team Goals and Themes

Previous Themes

  1. Move our test-automation code into each project’s main-development repository to enable faster feedback and visibility for developers
  2. Prototyping the future with new tools, skills, processes

New Themes

  1. Improve consistency and stability of automated tests
  2. Reduce dependency on buildmaster role

Individual Goals

Krupa

  1. Work with devs and ops to review and improve AMO's release process
  2. Work on Webextensions release for 48 to ensure cross-platform coverage
    1. Check if there are opportunities to engage with Chrome webextensions before the 48 release. Need to discuss with Amy and Dan before confirming on this.

Stephen

  1. Get a Dockererized OWASP ZAP (CLI) instance up and running against a staged instance of one of our key sites: either AMO, Mozilla.org, or MDN, in Web QA's Jenkins, on either/both a cronjob or on-demand, as goal
    • Document (i.e. blogpost[s]) the goals, the process, the progress, to try to help increase awareness
    1. DONE: https://blog.mozilla.org/webqa/2016/06/28/dockerized-owasp-zap-security-scanning-in-jenkins-part-two/ & http://159.203.196.21:8080/job/docker-zap-cli/22/console

Dave

  1. Set up UI functional tests for the add-ons website to run against pull requests
    • The UI functional tests currently live in https://github.com/mozilla/Addon-Tests and are run against deployed instances of the add-ons website. This deliverable will mean that UI functional tests will be run whenever a contributor submits a patch for consideration against an instance of the application including the change. This will reduce the feedback loop for failures, and will prevent regressions from being introduced.

Rebecca

  1. Ramp up and own Shavar deployments
  2. Learn and implement Docker container locally, assist with One and Done Docker-ization

Matt

  1. Dockerize One and Done
  2. MDN - Create a community oriented test plan

Open-ended Questions for Q2

  1. How can we increase community contribution?
    1. OneandDone goodfirstbugs import
    2. Bugsahoy
    3. Creating Outreachy tasks for evaluating candidates
    4. Clean up backlog of test automation bugs dashboard (and github issues)
  2. How can we improve GitHub issue and review discovery?
    1. Gaia has a history around this, might help to talk with them
    2. Bugzilla as much as possible just for history and discoverability
    3. Our dashboard could have bugzilla component tracking as well as GitHub Issues to try to combine
    4. Justin Potts had a redesign that might help
    5. Testrail test plans could generate manual and automated
Retrieved from "https://wiki.allizom.org/index.php?title=QA/Execution/Web_Testing/Goals/2016/Q2&oldid=1137977"