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

From MozillaWiki
< QA‎ | Firefox3‎ | TestPlan
Jump to navigation Jump to search
No edit summary
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Feature Content Handling: Web Protocol/Web Application Support Test Plan
<small>[[QA/Firefox3/TestPlan|&laquo; QA/Firefox3/TestPlan]]</small>


''' IN DRAFT -- Please post comments on the discussion page '''
Feature Content Handling: Web Protocol/Web Application Support Test Plan
 
= Overview =
''' IN DRAFT -- Please post comments on the discussion page '''
 
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).  
= Overview =
 
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.
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).
 
The list of popular data formats and protocols that this feature aims to handle:
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.
(TODO: link these to sites and determine completeness)
* hCalendar
The list of popular data formats and protocols that this feature aims to handle:
* hCard
* mailto:
* microformats
* hCalendar, (text/calendar), webcal:
* audio feeds
* hCard (text/vcard)
* video feeds
* geo links (application/vnd.google-earth.kml)
* RSS
* audio feeds (audio/x-mp3)
* text/calendar file type
* video feeds
* Image file type
* RSS
* Application file type
* Image file type
* text/vcard file type
* Application (executable) file type
* webcal: protocol
* callto: 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 =
= Platform and Configurations =
Line 57: Line 54:
* Thunderbird
* Thunderbird
||
||
* Gmail
* Gmail*
* Yahoo Mail
* Yahoo Mail*
* Hotmail
* Hotmail*
* AIM
* AIM
* Zimbra
|-
|-
| hCalendar, text/calendar, webcal:
|text/calendar  
hCalendar, webcal:
||  
||  
* Outlook 2007
* Outlook 2007
Line 78: Line 75:
* Mozilla Lightning or Sunbird  
* Mozilla Lightning or Sunbird  
||  
||  
* Google Calendar
* Google Calendar (not currently possible)
* Yahoo Calendar
* Yahoo Calendar (not currently possible)
* Hotmail Calendar
* Hotmail Calendar (not currently possible)
* Zimbra
* Zimbra (not currently possible)
* iCalShare
* iCalShare*
|-
|-
| hCard and text/vcard
| hCard and text/vcard
Line 99: Line 96:
* Entourage
* Entourage
||  
||  
* Gmail
* Find no web services that can import hCard or Vcard
* Yahoo Mail
* Use this site to download hcards: http://webindustry.com.au/view/members/111121/ (click on add to addressbook)
* Hotmail
* Zimbra
* Memotoo.com
* TODO: Other hCard enabled sites?
|-
|-
| [http://microformats.org/wiki/geo Geo Links] (type of microformat)
| * [http://microformats.org/wiki/geo Geo Links] (type of microformat)
* application/vnd.google-earth.kml
||  
||  
* TODO: Are there any thick clients for this?
* TODO: Are there any thick clients for this?
Line 118: Line 112:
|-
|-
| Audio Feeds
| Audio Feeds
* (audio/x-mp3)
||  
||  
* Windows Media Player
* Windows Media Player
Line 129: Line 124:
* iTunes
* iTunes
||
||
* [http://www.rhapsody.com Rhapsody Online]
* [http://www.jinzora.org Jinzora] (would require site specific information)
|-
|-
| Video Feeds
| Video Feeds
Line 150: Line 145:
||  
||  
* Thunderbird
* Thunderbird
* RSS reader in Vista Desktop
* <strike>RSS reader in Vista Desktop</strike> (not possible without changes to Firefox)
* [http://www.rssreader.com RssReader]
* [http://www.rssreader.com RssReader]
||
||
Line 185: Line 180:
* Preview
* Preview
||
||
* [http://view.samurajdata.se/ Online PDF Viewer]
* [http://view.samurajdata.se/ Online PDF Viewer*]
|-
|-
| callto:
| callto:
Line 201: Line 196:
|}
|}


= Major Test Areas =
Asteriks designate items with [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]
 
Major test areas are to test the applications in the table above with the proper type of content. We must ensure that the content types are handled appropriately in the handoff between Firefox and the third party application. We will probably use Litmus to test this.
 
We also must test the back-end architecture of this, to ensure the extensibility of the design.  We should do this using a test extension code that can be run on an automated basis and will use all the available APIs so that we have complete coverage even if not all of the current implementations of these content type handlers currently make use of those APIs today.
 
= Schedule/milestones =
 
Given the the current state of the UI design (in deep design) at the moment, I do not think that creating detailed Litmus test cases will be possible.  A general structure and base testcases for each type can be completed before the UI is totally finalized though.
 
Before the UI lands, we can work on the test extension/automated piece of this process so that we can test registering new content handlers. This part can coincide with the alpha 5 release.


TODO: Provide more details on schedule.
= Major Test Areas =


= References =
Major test areas are to test the applications in the table above with the proper type of content. We must ensure that the content types are handled appropriately in the handoff between Firefox and the third party application. We will probably use Litmus to test this.


* [[User:Ctalbert:Fx3:ContentHandling| General information regarding this feature]]
We also must test the back-end architecture of this, to ensure the extensibility of the design. We should do this using a test extension code that can be run on an automated basis and will use all the available APIs so that we have complete coverage even if not all of the current implementations of these content type handlers currently make use of those APIs today.
= Schedule/milestones =
UI and tests currently scheduled to be ready for Beta 1.


TODO: Include litmus groups, locations for automated test cases
= 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]

Latest revision as of 23:53, 16 November 2007

« QA/Firefox3/TestPlan

Feature Content Handling: Web Protocol/Web Application Support Test Plan

IN DRAFT -- Please post comments on the discussion page

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).

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:

  • mailto:
  • hCalendar, (text/calendar), webcal:
  • hCard (text/vcard)
  • geo links (application/vnd.google-earth.kml)
  • audio feeds (audio/x-mp3)
  • video feeds
  • RSS
  • Image file type
  • Application (executable) file type
  • 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.

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

We will want to test with the most popular web and platform specific applications for each high-priority type of format we want to support.

TODO: Is there a need to test cross platform products on more than one platform? Because at some point, you end up testing that product and not the content handler integration.

Protocol/File Type Windows Apps Linux Apps MacOSX Apps Web Applications
mailto:
  • Outlook 2007
  • Windows Mail (Outlook Express)
  • Thunderbird
  • KOrganizer
  • Evolution
  • Thunderbird
  • Mail.app
  • Thunderbird
  • Gmail*
  • Yahoo Mail*
  • Hotmail*
  • AIM
text/calendar

hCalendar, webcal:

  • Outlook 2007
  • Outlook 2003
  • Windows Calendar (Vista Only)
  • Mozilla Lightning or Sunbird
  • KOrganizer suite
  • Evolution
  • Mozilla Lightning or Sunbird
  • iCAL.app
  • Microsoft Entourage
  • Mozilla Lightning or Sunbird
  • Google Calendar (not currently possible)
  • Yahoo Calendar (not currently possible)
  • Hotmail Calendar (not currently possible)
  • Zimbra (not currently possible)
  • iCalShare*
hCard and text/vcard
  • Outlook 2007
  • Outlook 2003
  • Thunderbird
  • KOrganizer suite
  • Evolution
  • Eudora
  • Thunderbird
  • Addressbook.app
  • Thunderbird
  • Entourage
* Geo Links (type of microformat)
  • application/vnd.google-earth.kml
  • TODO: Are there any thick clients for this?
  • TODO: Are there any thick clients for this?
  • TODO: Are there any thick clients for this?
  • Flickr.com
  • Google Maps
Audio Feeds
  • (audio/x-mp3)
  • Windows Media Player
  • iTunes
  • Real-Player
  • TODO: Others?
  • iTunes
  • Jinzora (would require site specific information)
Video Feeds
  • Windows Media Player
  • iTunes
  • Democracy Player
  • Real-Player
  • Democracy Player
  • Helix Player
  • Quick Time
  • Democracy Player
RSS
  • Thunderbird
  • RSS reader in Vista Desktop (not possible without changes to Firefox)
  • RssReader
  • Firefox LiveMarks (possibly covered by other testing)
  • Bloglines
  • Google Reader
  • My Yahoo
  • MSN
Image Files
  • Paint
  • Gimp
  • Preview
  • Show in browser
PDF Files
  • Adobe Reader
  • Preview
callto:
  • Skype
  • Gizmo
  • Skype
  • Gizmo
  • Skype
  • Gizmo
  • Seem to be no online apps offering this service at this time

Asteriks designate items with Test Cases in Litmus

Major Test Areas

Major test areas are to test the applications in the table above with the proper type of content. We must ensure that the content types are handled appropriately in the handoff between Firefox and the third party application. We will probably use Litmus to test this.

We also must test the back-end architecture of this, to ensure the extensibility of the design. We should do this using a test extension code that can be run on an automated basis and will use all the available APIs so that we have complete coverage even if not all of the current implementations of these content type handlers currently make use of those APIs today.

Schedule/milestones

UI and tests currently scheduled to be ready for Beta 1.

References

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Firefox3/TestPlan/Content_Handling_-_Web_Protocol_and_Application&oldid=74966"