How WebQA Reponds to, Plans For, and Executes on, New Projects

1,635 views

Published on

Published in: Technology, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,635
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

How WebQA Reponds to, Plans For, and Executes on, New Projects

  1. 1. <ul>Stephen Donner <li>WebQA Pointy-hair
  2. 2. December 8, 2011 </li></ul>How WebQA responds to, plans for, and executes on new projects
  3. 3. <ul>Agenda </ul><ul><li>Current Processes + Tools
  4. 4. Planned Process + Tools
  5. 5. Planned Automation Coverage
  6. 6. Further Resources
  7. 7. Questions? Suggestions? Feedback? </li></ul>
  8. 8. Current Processes <ul><li>Weekly meeting with Web Production to discuss projects
  9. 9. (Project kick-off meeting with key stakeholders: IT, Webdev, InfraSec, WebQA, L10n, Engagement...)
  10. 10. Determine/assign WebQA owner
  11. 11. Determine type/extent of coverage, devise test plan
  12. 12. (Manually) Test
  13. 13. Lather, rinse, repeat (#5) </li></ul>
  14. 14. Current Tools https://wiki.mozilla.org/QA/Execution/Web_Testing#Useful_Tools <ul><li>Virtual Machines with operating system and browser-specific versions
  15. 15. HTML + RSS feed validators
  16. 16. Link checkers
  17. 17. Fuzzers (Netsparker + PowerFuzzer)
  18. 18. Selenium (scale to project needs)
  19. 19. Garmr (w/InfraSec) </li></ul>
  20. 20. Planned Process <ul><li>Meet with Web Production
  21. 21. (Kick-off meeting with key project stakeholders)
  22. 22. Determine/assign WebQA owner
  23. 23. Determine type/extent of coverage, devise test plan
  24. 24. Plug URL and functionality into automation templates
  25. 25. (Manually) Test </li></ul>
  26. 26. Planned Tools <ul><li>Plan is for as many (as possible) of the current tools -> hybrid Selenium + Python automation templates </li><ul><li>https://github.com/stupchiy/marketing-project-template
  27. 27. Culled from: </li><ul><li>https://wiki.mozilla.org/QA/Execution/Web_Testing/Project_Checklist
  28. 28. https://wiki.mozilla.org/QA/Execution/Web_Testing/Template </li></ul><li>Which cover... </li></ul></ul>
  29. 29. Planned Automated Coverage <ul><li>HTTP -> HTTPS redirects
  30. 30. Presence of a favicon
  31. 31. Presence of a 404 page with the correct HTTP status code
  32. 32. RSS-feed validation
  33. 33. (X)HTML validation
  34. 34. Link checking
  35. 35. Basic app performance, from Web Navigation Timing, through Boomerang: </li><ul><li>http://yahoo.github.com/boomerang/doc/api/navtiming.html </li></ul><li>...and much more, hopefully (JMeter, etc.) </li></ul>
  36. 36. Planned Automated Coverage ...running continuously
  37. 37. Resources <ul><li>WebQA wiki page: </li><ul><li>https://wiki.mozilla.org/QA/Execution/Web_Testing </li></ul><li>QMO page: </li><ul><li>https://quality.mozilla.org/teams/web-qa/ </li></ul><li>New-project automation template </li><ul><li>https://github.com/stupchiy/marketing-project-template </li></ul><li>Slide deck available from: </li></ul><ul><ul><li>http://www.slideshare.net/stephendonner </li></ul></ul>
  38. 38. Questions? Feedback? Suggestions? <ul><li>We're all ears! :-)
  39. 39. [email_address] (public mailing list)
  40. 40. #mozwebqa on irc.mozilla.org </li></ul>

×