QA/Execution/Web Testing/Browser Matrix: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
(Redirecting to QA/Execution/Web Testing/Template) |
|||
| (29 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
#REDIRECT [[QA/Execution/Web Testing/Template]] | |||
= '''Web browser testing matrix template''' = | = '''Web browser testing matrix template''' = | ||
{| class="fullwidth-table" | {| class="fullwidth-table" | ||
| Line 7: | Line 9: | ||
! Linux | ! Linux | ||
|- | |- | ||
| Firefox < 2.0.0. | | Firefox < = 2.0.0.12 | ||
| | | P1 | ||
| | | P1 | ||
| | | P1 | ||
| | | P1 | ||
|- | |- | ||
|- | |- | ||
| Internet Explorer 7 | | Internet Explorer 7 | ||
| | | P1 | ||
| | | P1 | ||
| | | '''N/A''' | ||
| | | '''N/A''' | ||
|- | |- | ||
| Internet Explorer 6 | | Internet Explorer 6 | ||
| | | P1 | ||
| '''N/A''' | | '''N/A''' | ||
| | | '''N/A''' | ||
| '''N/A''' | |||
|- | |- | ||
| Opera 9 | | Opera 9.25 | ||
| | | P2 | ||
| | | P2 | ||
| | | P2 | ||
| | | P2 | ||
|- | |- | ||
| Safari 2.0.4 | | Safari 2.0.4 / 3.0 | ||
| | | P1 | ||
| | | P1 | ||
| | | P1 | ||
| | | '''N/A''' | ||
|- | |- | ||
| Flock | | Flock 1.09 | ||
| | | P2 | ||
| | | P2 | ||
| | | P2 | ||
| | | P2 | ||
|} | |} | ||
Issues raised: | |||
1) Do we want to assume JS is always enabled?<br> | 1) Do we want to assume JS is always enabled?<br> | ||
* No; for P1s, test both enabled and disabled | |||
2) What about popups?<br> | 2) What about popups?<br> | ||
* Not a concern at the moment, but keep an eye out for it | |||
3) Should we just test defaults?<br> | 3) Should we just test defaults?<br> | ||
* Yes, unless specifically requested to do otherwise | |||
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> | ||
* TBD; varies with each project. Obviously, major functionality/layout issues would probably be a blocker. | |||
5) Escalation policy if we find major issues?<br> | |||
* There should be both a Project Lead and a QA Lead. QA Lead is responsible for signing off for his/her team, and for escalating issues. | |||
6) How do we report on our testing results? | |||
* There should be a Wiki table with the results of what was tested, by whom, and when. | |||
7) '''OPEN ISSUE''': What about screen readers and non-graphical browsers? Mobile testing? | |||
Latest revision as of 21:42, 3 July 2008
Redirect to:
Web browser testing matrix template
| Windows XP SP2 | Windows Vista | Mac | Linux | |
|---|---|---|---|---|
| Firefox < = 2.0.0.12 | P1 | P1 | P1 | P1 |
| Internet Explorer 7 | P1 | P1 | N/A | N/A |
| Internet Explorer 6 | P1 | N/A | N/A | N/A |
| Opera 9.25 | P2 | P2 | P2 | P2 |
| Safari 2.0.4 / 3.0 | P1 | P1 | P1 | N/A |
| Flock 1.09 | P2 | P2 | P2 | P2 |
Issues raised:
1) Do we want to assume JS is always enabled?
- No; for P1s, test both enabled and disabled
2) What about popups?
- Not a concern at the moment, but keep an eye out for it
3) Should we just test defaults?
- Yes, unless specifically requested to do otherwise
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'?
- TBD; varies with each project. Obviously, major functionality/layout issues would probably be a blocker.
5) Escalation policy if we find major issues?
- There should be both a Project Lead and a QA Lead. QA Lead is responsible for signing off for his/her team, and for escalating issues.
6) How do we report on our testing results?
- There should be a Wiki table with the results of what was tested, by whom, and when.
7) OPEN ISSUE: What about screen readers and non-graphical browsers? Mobile testing?