QA/Firefox3/TestPlan/Content Handling - Web Protocol and Application
Feature Content Handling: Web Protocol/Web Application Support Test Plan
IN DRAFT -- Please post comments on the discussion page
Contents
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: |
|
|
|
|
text/calendar
hCalendar, webcal: |
|
|
|
|
hCard and text/vcard |
|
|
|
|
* Geo Links (type of microformat)
|
|
|
|
|
Audio Feeds
|
|
|
|
|
Video Feeds |
|
|
|
|
RSS |
|
|
|
|
Image Files |
|
|
|
|
PDF Files |
|
|
||
callto: |
|
|
|
|
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.