Beruflich Dokumente
Kultur Dokumente
Execution
Expected Results
[Sidebar Feature 1]
Setup
Execution
Expected Results
[Sidebar Feature 2]
Setup
Execution
Expected Results
[Sidebar Feature n]
Setup
Execution
Expected Results
[Fullscreen Feature 1]
Setup
Execution
Expected Results
[Fullscreen Feature 2]
Setup
Execution
Expected Results
[Fullscreen Feature n]
Setup
Execution
Expected Results
TV App Updates
Complete this section when you are submitting an updated app with new features and bug fxes.
INSTRUCTIONS
List what is brand new in this app.
List updated features that may require re-testing.
Create new test cases, or update existing test cases, for new features and big fxes.
New Features
Please list each new feature of your TV App:
New
Features
1)
2)
3)
4)
Updated Features
Please list each updated feature of your TV App. Include any changes that may afect areas of the
app that have already been tested.
Updated
Features
1)
2)
3)
4)
[Updated Test Case Home Sidebar]
Setup
Execution
Expected Results
Execution
Expected Results
Execution
Expected Results
Execution
Expected Results
Execution
Expected Results
Execution
Expected Results
Execution
Expected Results
Acceptance Criteria
This section describes the criteria that TV Apps must pass to gain entry into the Yahoo Connected TV
Store.
INSTRUCTIONS
Check the box in the leftmost column when the criterion has been successfully tested.
Check the not applicable box (N/A) if a criterion has not been met (by design), and provide
an explanation in the comments column.
You must fll out the following sections:
Application to verify metadata, assets, and implementation criteria.
Stability to verify resource management, as in CPU, memory, and execution duration.
Usability to verify computer-human interaction conventions, multimedia experiences, and
graceful failures.
International to verify localization support if applicable.
Application Criteria
This section describes the application-level acceptance criteria.
Check
when
Complete
Name Description N/A
Comments if Not
Compliant or
Exemption
Requested
Bug Free Apps should contain no known bugs
nor open issues.
Max Size Apps should be no more than 2MB
unzipped on disk. This value should
be directly measurable in the WDK
using the du command.
Check
when
Complete
Name Description N/A
Comments if Not
Compliant or
Exemption
Requested
TV App
(Widget) ID
The TV App ID in the widget.xml
fle must be unique. Do not use
capital letters in the TV App ID. We
recommend using a reverse domain
name appended with meaningful
sub-domains, for example:
<identifier>com.yourcompany.ap
ps.tv.news</identifier>
The TV App ID should not change
when updating to a newer TV App
Version.
TV App
(Widget)
Version
A TV App Version must be at
minimum three integers separated by
periods: major number, minor
number, and micro number, for
example:
<version>0.9.5</version>
A TV App Version must increase with
each updated version (for example,
1.0.0 to 1.0.1) and not regress (for
example, 1.0.0 to 0.0.9).
Author
Name
The Author Name entered in the app
upload tool will be displayed in the
Yahoo Connected TV Store. This is
the publicly displayed text.
Author
Company
The Author Company entered in the
app upload tool will be displayed in
the Yahoo Connected TV Store. This
is the publicly displayed text.
Store TV
App
Description
The description entered in the app
upload tool will be displayed in the
Yahoo Connected TV Store. This is
the publicly displayed text.
Check
when
Complete
Name Description N/A
Comments if Not
Compliant or
Exemption
Requested
TV Store
Display
Images :
Store Icon
File / Store
Image File
For display in the Yahoo Connected
TV Store an app icon and a
sidebar/bookmark display are
required. The app icon is 44x44
pixels. Refer to the Quick Start Guide
for instructions on how to generate
these TV Store Display Images. The
app icon should be defned in the
widget.xml fle and located in the
Contents/Images/960x50/
directory, for example:
<image usage"#960x50.icon#
src"#Images/960x50/xxx.png#/>
TV App
(Widget)
File
(zipped)
The app must be zipped with the
following naming convention:
identifier-version.widget
The identifier and version
number in the zipped flename
matches the identifer and version
number in the widget.xml fle.
No Extra
Files
Zipped
The app must be zipped without
extra fles, for example there should
be no invisible fles (starting with . or
.$ ) nor %&um's.d' fles on Windows
nor .()$)tore fles and $$*+C,)-
folders on Mac.
No Extra
Images
The images bundled with an app
should only be those required for
backgrounds, controls, branding, or
the no-network state. Other images
should be fetched dynamically and
displayed (not stored).
Minimize
Persistent
Storage
Developers should work to minimize
persistent storage use as there are
limited write-cycles on the fash
memory array.
Check
when
Complete
Name Description N/A
Comments if Not
Compliant or
Exemption
Requested
Primary /
Single-
function
Apps must be primary/single-function
applications. Do not create a
launcher with sub-applications.
Create separate apps for each
application.
Bookmark
and
Sidebar
Required
Apps must have a bookmark and a
sidebar state at minimum.
No
Synchrono
us Calls
Apps must not make synchronous
calls.
No eval./ Use of the eval./ function in apps is
prohibited.
No
Obsolete
APIs
Use of obsolete APIs in apps is
prohibited.
No Third-
Party
Developme
nt Tools
The inclusion of third-party
development tools in your app code
is prohibited.
No XML
Schema
XML Schema fles (.xsd) are
prohibited.
Privacy
Policy
Developers must provide easy
access to a privacy policy from within
the app, including either the full text
of the policy or a URL to the policy
online.
Stability Criteria
This section describes the stability acceptance criteria.
Check
when
Complete
Name Description N/A
Comments if Not
Compliant or
Exemption
Requested
Stability The app should not crash, nor cause
the application engine or device to
crash. Apps must be able to run for
24 hours without memory leaks or
crashes. Apps must perform well
during stress tests (for example,
downloading images) in a test bed
with other running apps that
consume system resources.
Optimize
CPU
Utilization
Apps must not compromise the user
experience, and should be designed
to optimize CPU utilization.
Minimize
Memory
Utilization
TV platforms are very limited in
system resources. Apps must be
designed as light client applications
and minimize memory utilization.
Usability Criteria
This section describes the usability acceptance criteria.
Check
when
Complete
Name Description N/A
Comments if Not
Compliant or
Exemption
Requested
Remote
Keys
Trapping and releasing remote keys
(such as numeric keys) should only
be used when numeric entry in the
sidebar is required.
UI
Responsiv
eness
Navigation speed, page refreshes,
and general UI responsiveness is
comparable to Yahoo standard apps.
Fullscreen
Launch
The main bookmark should not
launch into fullscreen.
Audio in
Fullscreen
Audio should not run in the sidebar.
Audio is always presented in a
fullscreen view.
Video in
Fullscreen
Video should not run in the sidebar.
Video can be resized to an optimal
setting, but is always presented in a
fullscreen view.
Viewport
Video
Video displayed in viewport mode is
not distorted, cut-of or signifcantly
impacted. If a viewport is used in a
fullscreen state, video is displayed
optimally. Note: the video viewport
display is dependent on a particular
device partners media player.
Video
Events
Video apps must appropriately
handle the )%,0 and on0laylist1nd
events and lock
2,3tx.application.previous4iew./.
See this TV App Developer Forum
post for sample code.
Check
when
Complete
Name Description N/A
Comments if Not
Compliant or
Exemption
Requested
Closed
Captions
Video apps must provide closed
captioning as per all regulations.
Disconnect
ed State
When the network is down or the
server cannot be accessed, apps
must support an ofine state and
actively recover when re-entering the
online state.
Timeout
Gracefully
Apps need to timeout gracefully.
Timeouts should happen within a
minute or less.
Screensav
er Support
The screensaver timeout must be
implemented for the fullscreen view if
there is no user-interaction. The
screensaver timeout should be
triggered appropriately and cleared
when user interaction occurs. For
video apps, the screensaver timeout
is handled by the KONtx Framework.
Settings
Page
An About page in the App Settings
sidebar is required. Use the toolbox
control 2,3tx.views.+'out5ox to
implement the About page. The
App Settings sidebar is access by
the Green key on the remote control
or through the global toolbar. The
values for app author, version, and
contact information are required. For
users with questions about this app,
a customer care contact (email or
web address) is required.
Check
when
Complete
Name Description N/A
Comments if Not
Compliant or
Exemption
Requested
Focus Focus must never be lost regardless
of the apps state. Ensure that the
app uses either the KONtx
Framework focus methods or a
custom focus method in the sidebar
and fullscreen states.
Sign-in
Dialog
Apps that require sign-in or a PIN
entry to connect to a remote server
must provide the option to sign-in.
Internationalization Criteria
This section describes the internationalization acceptance.
Check
when
Complete
Name Description N/A
Comments if Not
Compliant or
Exemption
Requested
Localization
It is strongly recommended that apps
support internationalization. All text
strings within an app should have
calls to localized string functions. An
app can be viewed in multiple
languages appropriately.
TV App Approval Process
By submitting this form you are acknowledging that the specifed TV App has been tested and meets
these TV App Acceptance Criteria, and where there are exceptions, they are noted.
Both Yahoo and the device partners review your TV App using these Acceptance Criteria, and
when ready, approve your TV App for distribution in the Yahoo Connected TV Store.
Yahoo will confrm receipt and acceptance of this document and your TV Apps entry into the
Yahoo QA process.
Yahoo will provide periodic updates on QAs progress, including communication of bug lists,
Yahoo QA approval, and entry/feedback from the device partner QA teams.
See the TV App Approval Process Overview for more details. For any questions or status requests
please contact us at yctvsupport@yahoo-inc.com.
Addendum: How to Obtain an Encryption Registration Number (ERN)
The U.S. Commerce Departments Bureau of Industry and Security (BIS) requires an ERN as a pre-
condition to making certain encryption-controlled applications available for export, including those
released over the Internet. Before your TV App can be published in the Yahoo Connected TV Store,
you must obtain an ERN and provide it to Yahoo.
To request an ERN, please follow these steps:
1.Obtain a user account on the BIS Simplifed Network Application Process Redesign (SNAP-R)
system and a Company Identifcation Number (CIN) by visiting:
http://www.bis.doc.gov/snap/pinsnapr.htm
2.Once you have access to SNAP-R, follow the instructions under How To File an Encryption
Registration (see the frst fve paragraphs) at:
http://www.bis.doc.gov/encryption/question3_sub.htm
There is no fee for obtaining a SNAP-R account or ERN, but please allow plenty of time to complete
these governmental administrative processes.
For questions and additional information regarding SNAP-R access, please contact the BIS SNAP-R
Help Desk at snapr@bis.doc.gov or (202) 482-2227.