If you can't read please download the document
Upload
stephen-donner
View
1.245
Download
0
Embed Size (px)
Citation preview
How WebQA responds to, plans for, and executes on new projects 3.
4. Planned Process + Tools 5. Planned Automation Coverage 6. Further Resources 7. Questions?Suggestions?Feedback? 8. Current Processes
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
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
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
27. Culled from:
28. https://wiki.mozilla.org/QA/Execution/Web_Testing/Template Which cover... 29. Planned Automated Coverage
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:
...and much more, hopefully (JMeter, etc.) 36. Planned Automated Coverage ...running continuously 37. Resources
QMO page:
New-project automation template
Slide deck available from:
38. Questions?Feedback?Suggestions?
39. [email_address](public mailing list) 40. #mozwebqaon irc.mozilla.org