Your SlideShare is downloading. ×
How WebQA Reponds to, Plans For, and Executes on, New Projects
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

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

1,215
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,215
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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