Subscriber Product Engineering
Wireless Internet Test (WIT)


This site documents the test suites developed by Cingular Subscriber Product Engineering for use in testing and approving subscriber device browsers. This site mirrors the structure and content of the test suites accessible to devices and contains instructions on interpretation of results.


The purpose of this site is to provide the device manufacturer, browser supplier, carrier, wireless content standards, and the content developer communities a means of understanding the browser performance standards imposed by Cingular during the device approval process. Cingular intends that visibility of these tests and the interpretation of browser specifications leads to a convergence of browser performance and coding practices.

Usage Summary

Direct the device under test to and use a recommended PC browser (as described below) to simultaneously view this online guide at . Compare the idealized PC renderings of the various test pages and the descriptions of expected results to the behavior and appearance of the device.

Note: legacy IP-based URLs at and no longer work due to a server rehosting.

This online guide is organized with an active navigation tree to the left, a live representation of expected results in the middle, and test criteria on the right.

The navigation tree in the left frame is used to drive this site. Selecting a test case in the navigation tree brings up a live rendering of the page(s) under test in the middle frame and the expected results in the right rame. You may navigate a rendered test page in the middle frame but proceeding beyond the current test case will cause the expected results pane on the right to fall out of sync.

Relative Importance of Test Suites

The WIT root page contains several families of tests:

  • Mandatory MEdiaNet and HTTP tests:
    • Apps:
      • This small set of tests is mandatory for a phone that wants to qualify as MEdiaNet compliant from a visual rendering standpoint. These tests verify the minimal, basic elements of styling that are used in various tiers of M3 pages. The mandatory billing test is currently out of service pending the deployment of universal content that is insensitive to device UAstrings. Until that is ready, vendors should use devices with modified UAstrings that mimic released devices. mMode tests are strongly recommended because they test other standards-compliant rendering behavior in the context of more complex pages.
    • Common:
      • These tests exercise important markup-independent media content and HTTP protocol stack cookie/cache management functions. Libraries of image, video, and other content are available for download and playback/rendering/DRM testing on devices that support such types of content. HTTP tests verify that HTTP-layer header expiration and storage controls for cache and cookies are handled correctly. In addition, HTTP refresh and redirect commands are tested here. HTTP tests are given higher priority than the optional <meta> tag commands found in the individual markup language tests.
  • Java tests
    • MIDP 1.0:
      • This is a small family of basic tests that touch most MIDP 1.0 APIs. This suite has been retired but remains online for spot testing.
    • MIDP 2.0:
      • Cingular does not offer MIDP 2.0 tests for vendors but does currently require that vendors provide summary test results from Sun's JDTS for Cingular to review.
  • Important markup-independent content and stack tests
    • Core CSS:
      • This is an important subset of XHTML tags and CSS properties that is the goal for CSS-capable devices. This is an exhaustive test of a practical and finite subset of tags and properties that both fulfill the minimal mMode 2.0 menu rendering requirements and insure that the tags and properties are available in consistent ways that make them practical for content providers. (See Core CSS Spreadsheet below for more information)
  • Valuable for bug discovery and OMA specification compliance:
      • These are discrete tests of virtually every defined tag or attribute in the respective languages per the WAP/OMA language specifications. These tests are used extensively in exploring the breadth of capabilities of browsers but inherently limited in the depth of testing that is possible. For example, although every tag is tested at least once, it is not tested in the infinite nesting and usage permutations that are possible. Cingular recommends that browsers meet the WAP/OMA language requirements but recognizes that there is much leeway in deciding how much of each given language is essential or appropriate to a given device.
    • iMode remains online for spot testing but is not required. It is no longer being maintained and will be retired soon.

Recommended PC Browsers

No single PC browser fully captures the functionality required to run the navigation tree and render all of the markup languages. A different browser is recommended for different languages under test. Rendering is generally excellent for all of the recommended browsers with minor exceptions as noted in the online test guide for the affected test case.

Netscape | MS IE | Mozilla/Firefox | Opera

Special comments on Mozilla/Firefox: the extensible architecture of Mozilla/Firefox has resulted in a large number of freeware extensions that can be especially useful in device testing. Some specific plugins to consider:

  • User agent switcher: define your own user agent strings and quickly switch the announced UA string using a menu.

  • WML extension: an incomplete implementation of WML, but the convenience of being able to quickly view basic WML content without switching browsers makes it worthwhile.

In general, the following browser recommendations apply:

  • XHTML: Netscape, Mozilla/Firefox, or Opera are recommended because they are the only browsers that accept the XHTML MIME types. If XHTML source files are renamed with a .html extension they can be viewed with IE. In Opera, the dynamic navigation tree loads very slowly the first time, is static, and is fully expanded at all times. However, the navigation tree is still usable for navigation purposes.
  • CSS: Netscape, Mozilla/Firefox, or Opera are recommended because they are the only browsers that accept the XHTML MIME types and have high quality CSS rendering. If XHTML source files are renamed with a .html extension they can be viewed with IE. In Opera, the dynamic navigation tree loads very slowly the first time, is static, and is fully expanded at all times. However, the navigation tree is still usable for navigation purposes. CSS rendering quality varies slightly amongst these browsers but is generally excellent with only a few exceptions. Try switching to a different browser for a page that appears to be rendering incorrectly.
  • iHTML: All browsers are satisfactory for rendering purposes. However, DoCoMo extensions to cHTML are not recognized by PC browsers.
  • WML: For viewing live WML test pages in the context of this online guide, Opera is recommended because it has the highest quality and most functionally complete WML implementation. However, Opera's ability to handle some of the more advanced functions (variables, task shadowing, etc.) is incomplete. With the WML plugin, Mozilla/Firefox can do very basic WML rendering.

Release Notes and Change History

Latest release notes for all current test suites.

  • Application test suite: latest change 2/2/2009
  • XHTMLv2 test suite: latest change 2/2/2009
  • Core CSS test suite: latest change 9/4/2007
  • CSSv2 test suite: latest change 2/2/2009
  • iHTMLv2 test suite: latest change 1/30/2008
  • Commonv1 test suite: latest change 11/2/2007
  • MIDPv1 test suite: latest change 2/23/2006
  • WMLv2 test suite: 2/2/2009
  • SVG test suite: 10/30/2006

Test Case Listing

An MS Excel list (updated 7/20/07) of all test cases is available for use in constructing tracking documents.

Core CSS Spreadsheet

An MS Excel workbook defines the Core CSS XHTML tag and CSS property set. This document consists of 3 sections. The purpose of this workbook is to define a clear and finite subset of nested XHTML tag instances and the CSS properties that must apply to those tags. This type of definition does not currently exist in the OMA specifications and as a result, the specifications permit an infinite number of permutations and create an untestable situation.

  1. CSS Property and XHTML Tag Applicability
    This grid defines the XHTML tag subset (~24 tags) and CSS properties (~48 properties) that are deemed essential for mMode 2.0 and for a device to qualify as "enhanced". The grid defines which property must apply to which tag subject to the mandatory instances of the tag in the Nesting Relationship spreadsheet. The goal of the applicability matrix is to define a useful and broad application of a property (e.g. color) across as many essential tags as possible.
  2. Nesting Relationships of Styleable XHTML Tags
    This collapsible nested spreadsheet identifies all of the desired instances of tags for which the styles defined in the CSS Property and XHTML Tag Applicability grid must apply. The infinite number of instances of tags that are permitted by XHTML parent-child nesting relationships demands that a finite minimum family be defined for testability. The chosen family of tag instances eliminates obvious recursions (e.g. <div> inside <div>) and complex instances for which a simpler usage is available (e.g. <link> in <p> in <body> rather than <link> in <span> in <p> in <div> in <body>). Some redundancy has been allowed for essential block elements, i.e. it was deemed desirable to allow tables to exist as a top-level element in the body as well as within a <div> and a <form>.
  3. Tag Child Relationships
    This informative chart reflects the allowed parent-child relationships amongst tags as defined in the XHTML specifications. Some tags can be members of recursive nestings, others represent terminal tags.

Of the ~24 tags, there are ~100 instances of usage resulting from nesting permutations that Cingular has identified as important. Each tag is typically expected to support about 30 properties on average (note that some properties are illegal on some tags). This results in a total of approximately 3000 discrete applications of CSS that are defined in the Core CSS definitions and exhaustively tested by the Core CSS tests.

Note that the workbook also contains supplemental definitions of required attribute values such as color specifications (RGB, hex, named colors), units of measure (em, ex, px, %), values (integer, float), etc. Some of these are tested in depth, but the order of magnitude increase in test scope that would result from exercising all of these values makes a thoroughly exhaustive test impractical. Thus, some values are only sampled during testing.

Legacy Tests

All legacy test suites have been taken off line because they are no longer being maintained and have known coverage gaps.

Offline (online guide) (WML test suite)
Offline (online guide) (XHTML test suite)
Offline (online guide) (iHTML test suite)

Recent Changes

Feb 11, 2010: Added 302 redirect test(httpredirectext.xhtml)page to test 302 redirect for rtsp and tel URL's

Nov 23, 2009: Added Qpass cookie test page. Modified linktel page to support two way audio test

Aug 25, 2009: XHTML imagedim now supports dynamic image generation for any size image

Feb 2, 2009: WIT Guide clarifications and corrections made to App, XHTML, WML, and CSS rendering tests.

Jan 14, 2009: CSS cascsheet @import test has been made optional.

Apr 15, 2008: SPE test header sniff utilities all converted to HTML for improved PC compatibility.

Feb 29, 2008: WIT Guide documentation for many test cases clarified. Upcoming 10776 test specs reference mandatory WIT tests, and guide defines critical and mandatory behaviors.

Jan 30, 2008: Interlaced PNG has been removed from imagetype tests.

Nov 30, 2007: Doc number 14652 test case 4.14.1 WML and 4.14.2 are to be marked failed if any "14652 critical" test fails. See online WIT documentation for affected test cases.

Nov 7, 2007: JAM HTTP snoop tool added in WIT > SPETest > Header for sniffing headers issued by JAM during JAR get

Nov 7, 2007: Real-hosted video test links added to Apps.

Nov 2, 2007: httperror added to test all 4xx and 5xx http error codes.

Oct 29, 2007: Password access to apps directory reinstated for authorized users.

Oct 29, 2007: Ongoing network problems causing intermittent outages. Under analysis.

Sept 4, 2007: CSS input format mask case sensitivity removed

Sept 4, 2007: mmodecollapse default border separation clarified.

August 20, 2007: struccard.wml newcontext test retired.

August 9, 2007: linkanchor accesskey relaxed to allow keys to be mapped to UI functions

August 6, 2007: httpredirect passes if 2000 byte relative URL succeeds. Post vs Get method errors no longer important.

August 3, 2007: linklen tests in each language allow for custom lengths

July 20, 2007: Firethorn Mobile Banking SSL test links added to Apps.

June 8, 2007: My Account test URL updated.

June 5, 2007: common httprefresh now uses no-cache

Apr 25, 2007: common httpcacheobj added to test expirable cached images

Feb 19 , 2007: MobiTV/Radio test apps added to Apps suite.

Jan 17, 2007: Legacy server at has been retired.

Oct 30, 2006: SVG test suites added.

Oct 10, 2006: proxy connection diagnostic added to cookie tests

Oct 7, 2006: Ideal MediaNet bubbles updated.

Oct 3, 2006: cookie max-age tests modified.

Sep 19, 2006: more SSL sites added to linkanchor

Sep 12, 2006: entityother extended with upper case Spanish characters.

Sep 12, 2006: Updated M3 pages added to App suite.

Jul 21, 2006: linkanchor SSL tests point to new server

Jul 7, 2006: linkanchor HTTPS links are briefly out of service due to server SSL problem

Jul 7, 2006: structemp.wml status results clarified.

Jun 29, 2006: CSS fontsize.xhtml clarified with better pixel and point size tests

Jun 13, 2006: struccard.wml revised

Jun 3, 2006: minor nesting error corrected in mmodelayout

Apr 19, 2006: linkanchor tests modified

Apr 3 , 2006: linkvideo H.263, H.264, MPEG-4, AMR-NB, AAC-LC variants added.

Mar 14, 2006: fontsize test corrected.

Feb 23, 2006: Signed apps added to main site.

Feb 17, 2006: My Account SSL test page added.

Feb 9, 2006: linkmailto redesigned to use forms.

Feb 9, 2006: iHTML suite will be retired soon.

Nov 23, 2009: Qpass cookie test page is added.

Comments, suggestions for additional tests, or questions related to these tests should be directed to Katy Bhat at

©2002, 2003, 2004 Cingular Wireless, All Rights Reserved.
Acceptable Use Policy    Site Access Agreement    Privacy Policy    Consumer Code