QA/Execution/Web Testing/Browser Matrix: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 8: Line 8:
|-
|-
| Firefox < 2.0.0.6
| Firefox < 2.0.0.6
| foo
| P1


| foo2
| foo2
Line 17: Line 17:
|-
|-
| Internet Explorer 7
| Internet Explorer 7
| foo
| P1
| foo2
| P1
| foo3
| '''N/A'''
| foo4
| foo4
|-
|-
| Internet Explorer 6
| Internet Explorer 6
| foo
| P1


| '''N/A'''
| '''N/A'''


| foo3
| '''N/A'''


| foo4
| foo4
Line 46: Line 46:
|-
|-
| Flock 0.9
| Flock 0.9
| foo
| P1
| foo2
| foo2
| foo3
| foo3

Revision as of 12:48, 22 August 2007

Web browser testing matrix template

Windows XP SP2 Windows Vista Mac Linux
Firefox < 2.0.0.6 P1 foo2 foo3 foo4
Internet Explorer 7 P1 P1 N/A foo4
Internet Explorer 6 P1 N/A N/A foo4
Opera 9 foo foo2 foo3 foo4
Safari 2.0.4 foo foo2 foo3 foo4
Flock 0.9 P1 foo2 foo3 foo4

Open issues:

1) Do we want to assume JS is always enabled?
2) What about popups?
3) Should we just test defaults?
4) What's considered a blocker? Do we want a tier system, much like Yahoo! has, WRT 'http://developer.yahoo.com/yui/articles/gbs/ graded support'?
5) Escalation policy if we find major issues?
6) How do we report on our testing results?