QA/Execution/Web Testing/Browser Matrix: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
No edit summary |
|||
Line 25: | Line 25: | ||
| foo | | foo | ||
| | | '''N/A''' | ||
| foo3 | | foo3 |
Revision as of 18:22, 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 'support'?