MozillaWiki

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

Page Discussion

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

Revision as of 23:53, 16 November 2007

826 bytes added ,  16 November 2007
no edit summary
No edit summary
No edit summary
 
(14 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
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).  
 
''' IN DRAFT -- Please post comments on the discussion page '''
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.
 
= Overview =
The list of popular data formats and protocols that this feature aims to handle:
(TODO: link these to sites and determine completeness)
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).
* hCalendar
* hCard
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.
* microformats
* audio feeds
The list of popular data formats and protocols that this feature aims to handle:
* video feeds
* mailto:
* RSS
* hCalendar, (text/calendar), webcal:
* text/calendar file type
* hCard (text/vcard)
* Image file type
* geo links (application/vnd.google-earth.kml)
* Application file type
* audio feeds (audio/x-mp3)
* text/vcard file type
* video feeds
* webcal: protocol
* RSS
* callto: protocol
* Image file type
 
* Application (executable) file type
 
* callto: protocol
 
= Scope of planned testing =
= 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.
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.
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.
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 41: Line 41:
! Protocol/File Type !! Windows Apps!! Linux Apps !! MacOSX Apps !! Web Applications
! Protocol/File Type !! Windows Apps!! Linux Apps !! MacOSX Apps !! Web Applications
|-
|-
| hCalendar, text/calendar, webcal:
| 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 2007
Line 56: Line 75:
* Mozilla Lightning or Sunbird  
* Mozilla Lightning or Sunbird  
||  
||  
* Google Calendar
* Google Calendar (not currently possible)
* Yahoo Calendar
* Yahoo Calendar (not currently possible)
* WebCalendar
* Hotmail Calendar (not currently possible)
* (TODO): Is there a windows calendar for hotmail?
* Zimbra (not currently possible)
* TODO: Others?
* iCalShare*
|-
|-
| hCard and text/vcard
| hCard and text/vcard
Line 76: Line 95:
* Thunderbird
* Thunderbird
* Entourage
* Entourage
|| TODO: What is available for web-based contact management software?
||  
* LDAP Directories?
* Find no web services that can import hCard or Vcard
* Use this site to download hcards: http://webindustry.com.au/view/members/111121/ (click on add to addressbook)
|-
|-
| Geo Links (type of microformat)
| * [http://microformats.org/wiki/geo Geo Links] (type of microformat)
* application/vnd.google-earth.kml
||  
||  
* TODO: ??
* TODO: Are there any thick clients for this?
||
||
* TODO: ??
* TODO: Are there any thick clients for this?
||
||
* TODO: ??
* TODO: Are there any thick clients for this?
||
||
* Google Earth
* Flickr.com
* Google Maps
* Google Maps
* Mapquest
|-
|-
| Audio Feeds
| Audio Feeds
* (audio/x-mp3)
||  
||  
* Windows Media Player
* Windows Media Player
Line 98: Line 119:
* TODO: Others?
* TODO: Others?
||
||
* TODO:??
* Real-Player, Real-Player Firefox plugin
* Real-Player?
* [https://player.helixcommunity.org/ Helix player]
||
||
* iTunes
* iTunes
* Real-Player
* QuickTime?
||
||
* TODO: Web Jukebox?
* [http://www.jinzora.org Jinzora] (would require site specific information)
|-
|-
| Video Feeds
| Video Feeds
||
||
* Windows Media Player
* Windows Media Player
* iTunes (maybe)
* iTunes  
* Democracy Player
* Democracy Player
* Real-Player?
* Real-Player
||
||
* Democracy Player
* Democracy Player
* TODO: Others?
* Helix Player
||
||
* Quick Time
* Quick Time
* Democracy Player
* Democracy Player
* Real-Player?
||
||
* TODO: Can you send a feed to an online based site like UTube?
* MSN Video
* [http://peekvid.com PeekVid]
|-
|-
| RSS
| RSS
||  
||  
* Thunderbird
* Thunderbird
* Vista sidebar reader...TODO: what is the '''name''' of that thing
* <strike>RSS reader in Vista Desktop</strike> (not possible without changes to Firefox)
* Others?
* [http://www.rssreader.com RssReader]
||
||
* Thunderbird
* Thunderbird
* TODO: Others?
* [http://www.gnome.org/projects/straw/ Straw]
||
||
* Thunderbird
* Thunderbird
* Mac Dashboard widgets?
* Mac Dashboard widgets
* TODO: Others?
* [http://www.newsfirerss.com/ NewsFire]
* [http://www.newsgator.com/Individuals/NetNewsWire/ NetNewsWire]
||
||
* Firefox LiveMarks (possibly covered by other testing)
* Firefox LiveMarks (possibly covered by other testing)
Line 140: Line 160:
* Google Reader
* Google Reader
* My Yahoo
* My Yahoo
* MSN
|-
|-
| Image Files
| Image Files
Line 149: Line 170:
* Preview
* Preview
||
||
* TODO: Online image viewers? Flickr?
* Show in browser
* TODO: Show in browser?
|-
| PDF Files
||
* Adobe Reader
||
* [http://www.gnome.org/projects/evince/ Evince]
||
* Preview
||
* [http://view.samurajdata.se/ Online PDF Viewer*]
|-
|-
| callto:
| callto:
Line 163: Line 193:
* Gizmo
* Gizmo
||
||
* TODO: Pure online calling software?
* Seem to be no online apps offering this service at this time
|}
|}
= 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 =
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.
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]


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]
Samuelsidler
1,457

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/57836...74966"