QA/Firefox3.5/ViewSource Testplan: Difference between revisions
| Line 22: | Line 22: | ||
List areas that will NOT be covered (by developer, third party, etc.) | List areas that will NOT be covered (by developer, third party, etc.) | ||
Describe how testcases will be created (litmus, mochitests, reftests, gristmill, 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 = | = Schedule Scoping = | ||
Revision as of 23:23, 14 November 2008
- 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)
References
Include notes, links, specs, relevant bugs