QA/Execution/Web Testing/Browser Matrix: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
No edit summary |
|||
| Line 58: | Line 58: | ||
3) Should we just test defaults?<br> | 3) Should we just test defaults?<br> | ||
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'?<br> | 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'?<br> | ||
5) Escalation policy if we find major issues? | 5) Escalation policy if we find major issues?<br> | ||
6) How do we report on our testing results? | |||
Revision as of 11:30, 22 August 2007
Web browser testing matrix template
| Windows XP SP2 | Windows Vista | Mac | Linux | |
|---|---|---|---|---|
| Firefox < 2.0.0.6 | foo | foo2 | foo3 | foo4 |
| Internet Explorer 7 | foo | foo2 | foo3 | foo4 |
| Internet Explorer 6 | foo | N/A | foo3 | foo4 |
| Opera 9 | foo | foo2 | foo3 | foo4 |
| Safari 2.0.4 | foo | foo2 | foo3 | foo4 |
| Flock 0.9 | foo | 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?