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?

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'?

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?

@@ Line 1: / Line 1: @@
+#REDIRECT [[QA/Execution/Web Testing/Template]]
 = '''Web browser testing matrix template''' =
 {| class="fullwidth-table"
@@ Line 7: / Line 9: @@
 ! Linux
 |-
-| Firefox < = 2.0.0.7
+| Firefox < = 2.0.0.12
 | P1
@@ Line 31: / Line 33: @@
 | '''N/A'''
 |-
-| Internet Explorer 5.2
+| Opera 9.25
-| '''N/A'''
-| '''N/A'''
-| EOL?
-| '''N/A'''
-|-
-| Opera 9.23
 | P2
 | P2
@@ Line 50: / Line 46: @@
 | '''N/A'''
 |-
-| Flock 0.9.1.0
+| Flock 1.09
 | P2
 | P2