QA/Firefox3/TestPlan/Content Handling - Web Protocol and Application: Difference between revisions

QA/Firefox3/TestPlan/Content Handling - Web Protocol and Application (view source)

Revision as of 22:37, 5 July 2007

61 bytes removed , 5 July 2007

no edit summary

Ctalbert

Confirmed users

3,816

edits

@@ Line 1: / Line 1: @@
 Feature Content Handling: Web Protocol/Web Application Support Test Plan
-	''' IN DRAFT -- Please post comments on the discussion page '''
+''' IN DRAFT -- Please post comments on the discussion page '''
-	= Overview =
+= Overview =
-	This feature enables Firefox to hand off content to both web applications (like Google Calendar) and to local applications that have been registered to handle this type of data (like Mozilla Sunbird).
+This feature enables Firefox to hand off content to both web applications (like Google Calendar) and to local applications that have been registered to handle this type of data (like Mozilla Sunbird).
-	There is a large number of such data types and web/local application types. For our testing, we will try to cover all of the most likely types and popular applications.
+There is a large number of such data types and web/local application types. For our testing, we will try to cover all of the most likely types and popular applications.
-	The list of popular data formats and protocols that this feature aims to handle:
+The list of popular data formats and protocols that this feature aims to handle:
-	(TODO: link these to sites and determine completeness)
+* mailto:
-	* hCalendar
+* hCalendar, (text/calendar), webcal:
-	* hCard
+* hCard (text/vcard)
-	* microformats
+* geo links (application/vnd.google-earth.kml)
-	* audio feeds
+* audio feeds (audio/x-mp3)
-	* video feeds
+* video feeds
-	* RSS
+* RSS
-	* text/calendar file type
+* Image file type
-	* Image file type
+* Application (executable) file type
-	* Application file type
+* callto: protocol
-	* text/vcard file type
-	* webcal: protocol
-	* callto: protocol
+= Scope of planned testing =
+It is not possible to test every version of every application on every OS for every type of feed/format combination. Doing so would result in a gigantic test matrix. We have instead taken the view to test the most prominent applications for each of these items on each platform. We will also run some automated tests against the code to verify that extension authors have the required abilities to create their own protocol handlers and that users can associate other applications to handle specific types of content.
-	= Scope of planned testing =
+Also, it is expected that Firefox will automatically detect the proper local applications that are registered to handle this type of content. So, in addition to the "popular" applications, we should also test linking in other applications via the OS and ensure that they are properly detected and handled in Firefox.
-	It is not possible to test every version of every application on every OS for every type of feed/format combination. Doing so would result in a gigantic test matrix. We have instead taken the view to test the most prominent applications for each of these items on each platform. We will also run some automated tests against the code to verify that extension authors have the required abilities to create their own protocol handlers and that users can associate other applications to handle specific types of content.
+However, if the user uses Firefox to set up a linkage for a particular type of data, it is '''not''' currently expected that Firefox will write that information out to the OS. This could change post alpha 5.
-	Also, it is expected that Firefox will automatically detect the proper local applications that are registered to handle this type of content. So, in addition to the "popular" applications, we should also test linking in other applications via the OS and ensure that they are properly detected and handled in Firefox.
-	However, if the user uses Firefox to set up a linkage for a particular type of data, it is '''not''' currently expected that Firefox will write that information out to the OS. This could change post alpha 5.
 = Platform and Configurations =
@@ Line 209: / Line 204: @@
 = Schedule/milestones =
-	UI and tests currently scheduled to be ready for Beta 1.
+UI and tests currently scheduled to be ready for Beta 1.
 = References =
 * [[User:Ctalbert:Fx3:ContentHandling| General information regarding this feature]]
 * [http://litmus.mozilla.org/show_test.cgi?searchType=by_category&product_id=1&branch_id=15&testgroup_id=56&subgroup_id=820 Test Cases in Litmus]