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

From MozillaWiki
Jump to navigation Jump to search
Line 7: Line 7:
! Linux
! Linux
|-
|-
| Firefox < 2.0.0.6
| Firefox < = 2.0.0.6
| P1
| P1


| foo2
| P1


| foo3
| P1
| foo4
| P1
|-
|-
|-
|-
Line 33: Line 33:
|-
|-
| Opera 9
| Opera 9
| foo
| P2
| foo2
| P2
| foo3
| P2
| foo4
| P2
|-
|-


| Safari 2.0.4
| Safari 2.0.4
| foo
| P1
| foo2
| P1
| foo3
| P1
| foo4
| '''N/A'''
|-
|-
| Flock 0.9
| Flock 0.9

Revision as of 19:59, 22 August 2007

Web browser testing matrix template

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

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?