QA/Firefox3.5/ViewSource Testplan: Difference between revisions

QA/Firefox3.5/ViewSource Testplan (view source)

Revision as of 01:30, 19 November 2008

66 bytes removed , 19 November 2008

→‎Linkification of HREF and SRC URLs in Firefox 3.1

Cbartley

213

edits

@@ Line 62: / Line 62: @@
 A two pronged approach will be used for testing the linkification feature: Automated testing (using Mochitests) wherever possible, and manual testing elsewhere.  Since view source is heavily used by web developers and linkification has been a much requested extension, we can reasonably expect good test coverage from beta users.
-# Does linkification work at all?  Mochitest can load a view-source page into an IFRAME and then scan the DOM for anchor elements.  Anchor elements will only be present if linkification is in effect.
+==== Mochitests ====
-# Are links being built correctly?  A Mochitest can examine the HREF attributes on anchor elements inside the view source page and can verify they are being built correctly.
-# Do back and forward work? It might be possible to test this using the IFRAME approach and triggering back and forward programmatically.  This won't test key bindings, but key bindings are simple to test manually.
-# Do back and forward key bindings work?  This really needs to be tested manually.
+The basic linkification functionality should be amenable to automated testing with Mochitests.  The proposed approach is to embed view-source pages into Mochitest pages using IFRAME elements.  Once a view-source URL has loaded into an IFRAME, the test code in the Mochitest page can examine its DOM looking for anchor elements -- currently the only way an anchor element can end up in the DOM of a view-source page is through the linkification feature.
-# Entity expansion is not carried out when view-source URLs are built (it should be).
+By using a carefully crafted HTML page as the target of the view-source URL in the IFRAME it should be possible to test most of the basic aspects of linkification, starting with "Does linkification work at all", and moving to some of the thornier cases like entity expansion.  Most of the test cases described in the section '''URL types''' below should be amenable to this sort of testing.
-# URLs that point to non-text resources (most especially images) are still turned into view-source URLs which will try to interpret them as text.  Since we don't need the mimetype to know for sure what sort of resource is being referenced, a smarter view-source handler is needed.  A view-source URL pointing to an image should be rendered as a regular URL pointing to an image would be.  This might be difficult to test programmatically, but it's pretty easy to test manually.
+==== Manual Testing ====
+Some aspects of the linkification feature will most likely need to be tested manually, at least in the near term.  In particular history navigation -- i.e. <Back> and <Forward> will be easier to test manually.  See the table in the ''Navigation through history'' section below.
 ==== URL types ====