QA/Firefox3.5/ViewSource Testplan

« QA/Firefox3.1/TestPlan

Feature <abc> Test Plan

Overview

 Provide an abstract of the feature and the test strategy.  
 Are there particular challenges with testing this feature?

The View Source feature displays the source HTML of a page as the original text, not as rendered markup. The related View Selection Source command displays just the source for the selected range on the page.

View Page Source may be invoked several ways. 1. Select View >> Page Source from the main menu. 2. Select View Page Source from the page context menu. 3. Press Ctrl-U/Cmd-U on the keyboard.

View Selection Source may only be invoked from the context menu when some content on the page is currently selected.

Test Strategy

 List major areas of test coverage
 List areas that will NOT be covered (by developer, third party, etc.)
 Describe how testcases will be created (litmus, mochitests, reftests, gristmill, etc..)

There are three areas of testing.

1. The source displayed must exactly match the source text originally retrieved by the browser. (Question: Can we really guarantee this?) 2. Syntax highlighting is correct. 2a. Syntax highlighting is correct for each type of token for HTML syntax that's correct. 2b. Syntax that is incorrect is highlighted appropriately. 3. The values of SRC and HREF attributes are always treated as URLs, and are represented in the view source display as actual clickable URLs. If a URL is to an HTML file, then clicking the URL should display the contents at that URL as source. For other types of resources, the effect of clicking the URL should be the same as clicking it in the main window. (Latter doesn't make sense for e.g. stylesheets, etc.)

Schedule Scoping

 Estimate amount of time it will take to complete feature
 (Consider nightly builds, security reviews, bugs turnaround time)

The basic view source feature has existed for over 10 years. The most recent addition is the linkification of URL attributes. It is the latter feature that is most in need of testing at this time.

The linkification feature is "complete" at this time, but exhibits a number of bugs, some of them fairly severe. Some of these "bugs" are arguably missing sub-features rather than bugs, but at this point the distinction is probably meaningless.

The linkification feature is new for Firefox 3.1. The amount of time to "complete" the feature has been arbitrarily declared as the amount of time left on 3.1. Bugs/missing sub-features will be triaged and the most important ones will be fixed first. It should be possible to fix all the serious bugs and, hopefully, implement the most serious missing subfeatures in the time remaining. Bugs or missing sub-features which are "annoying" rather than serious can wait until Firefox 3.2 to be addressed if necessary.

References

 Include notes, links, specs, relevant bugs

• bug 15372 view-source: URLs need overhaul
• bug 463176 NS_ERROR_FACTORY_NOT_REGISTERED from nsIDocShellHistory.useGlobalHistory opening view source
• bug 464314 view-source link-browsing doesn't decode entities
• bug 464388 View Source linkification triggers "ASSERTION: Error: no token allocator"
• bug 464727 Incorrect linkification of view-source if newline follows the linkinfied attribute.
• bug 464857 view-source link-browsing is not perfect