Wireless Application Environment Version 2.0 and Wireless Application Environment Defined Media Type Specifications
ISSUE : waeJK1ts_010717
Copyright © 1999, 2000, 2001 Wireless Application Forum. Ltd. All Rights Reserved.
Preface
Preface
This document contains the test specification for the WAP June 2001
release of the:
- Wireless Application Environment Specification (Version 2)
- version WAP-236-WAESpec-20011109-a.pdf
- Wireless Application Environment Defined Media Type Specification
- version WAP-237-WAEMT-20010515-d.pdf
The specification is organized such that there is a section for each section of
the WAP WAE specifications in which assertions can be found. For each
assertion in the WAP WAE specification a corresponding entry in this test
specification contains the following elements:
For each assertion in the specifications, a corresponding entry in this test
specification contains the following elements:
| ID: |
The name by which the test is known |
| Class: |
An assertion Class as defined in IEEE Std 1003.3. These types are: |
| A |
A mandatory, testable assertion. |
| B |
A mandatory, but untestable assertion. |
| C |
An optional, testable assertion. |
| D |
An optional, but untestable assertion. |
|
| Scope: |
If an assertion is type C or D, this entry describes the option that needs
to be supported in order to activate the test. |
| Text: |
The text of the assertion and a reference to the source specification
from which the assertion is derived. |
| Note: |
Any supplementary information associated with the assertion. For example
it may suggest a strategy for the test implementation of the assertion
or it may propose rationale as to why a test is classified as untestable.
|
This specification uses the following conventions for convenience:
- Element and attribute names are in UPPERCASE.
- References to DTD entities are prefixed with percent sign (e.g. %PCDATA).
- Literal text is enclosed in quotation marks.
There are no testable assertions in this section.
Extra assertions that cover the individual media types or file extensions
are included in the specifications from which they are derived.
| ID: |
wae2/media/types/1 |
| Class: |
A |
| Text: |
A user agent must use the MIME media type to determine the
content data type of the document. [Wireless Application Environment Specification section 6.1] |
| Note: |
Send a document containing a supported content type header
(e.g. application/wml+xml) and a wrong extension. Make sure that the
document is processed. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
Further assertions related to WAP CSS can be found in the assertion
specification specific to WAP CSS.
| ID: |
wae2/media/css/cssrules/1 |
| Class: |
C |
| Scope: |
"The device DOES support WAP CSS" |
| Text: |
When a WAE user agent allows authors to control appearance
of the document it must support WAP CSS. [Wireless Application Environment Specification section 6.3.2] |
| Note: |
Send a very simple WAP document
(e.g. test ) and make sure
that the text is aligned on the right side. Otherwise if no common
properties can be defined, this test should be as untestable. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
| ID: |
wae2/media/wmlscript/wmlsrules/1 |
| Class: |
A |
| Text: |
When a WAE user agent requests content that includes
WMLScript it must process it. [Wireless Application Environment Specification section 6.4.2] |
| Note: |
Get the user to access a document that contains WMLScript.
This could just set a variable. Then show a page that displays this
variable. Make sure that the page is displayed and the variable shown
as set. |
|
| ID: |
wae2/media/wmlscript/wmlsrules/2 |
| Class: |
A |
| Text: |
When a WAE user agent requests content that includes
WMLScript Libraries it must process it. [Wireless Application Environment Specification section 6.4.2] |
| Note: |
Get the user to access a document that contains WMLScript
libraries. Make sure that the page is displayed and the WMLScript
has been executed correctly. |
|
|
|
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
| ID: |
wae2/media/images/gcrules/1 |
| Class: |
C |
| Scope: |
"The client DOES support graphical images" |
| Text: |
When a WAE user agent supports images it must support
wireless bitmap. [Wireless Application Environment Specification section 6.6.2] |
| Note: |
Get the user to access a document that contains a wireless
bitmap. Make sure that the bitmap image is shown. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
| ID: |
wae2/media/vcard/cardrules/1 |
| Class: |
C |
| Scope: |
"The client DOES support the electronic business card format (vCard)" |
| Text: |
When a user agent supports vCard exchange through WSP and
W-HTTP it must support the 'text/x-vCard' MIME type. [Wireless Application Environment Specification section 6.7.2] |
| Note: |
Get the user to select a link that loads content with the
MIME type 'text/x-vCard' and an extension of '.vcf'. Make sure that
the user agent does not display the error that the MIME type is not
supported. We could also make sure that the user agent declares the
'text/x-vCard' type in its accept header, but this would not actually
check that it does support it, just that it claims to. |
|
| ID: |
wae2/media/vcard/cardrules/2 |
| Class: |
D |
| Scope: |
"The client DOES support the electronic business card format (vCard)" |
| Text: |
When a user agent supports vCard exchange through WDP it
must support vcard on the port assigned in WDP
(unsecure : 9204, secure : 9206). [Wireless Application Environment Specification section 6.7.2] |
| Note: |
Untestable as we can not support direct communication with
clients using WDP datagrams. All of our test suits are based on HTTP
communication. |
|
| ID: |
wae2/media/vcard/cardrules/3 |
| Class: |
C |
| Scope: |
"The client DOES support the electronic business card format (vCard)" |
| Text: |
When a WAE user agent accesses vCard content it must be able
to displaythe NAME property. [Wireless Application Environment Specification section 6.7.2] |
| Note: |
Get the user to access a vCard with a known NAME property
from the device under test. Make sure that the value in the NAME
property is displayed. |
|
| ID: |
wae2/media/vcard/cardrules/4 |
| Class: |
C |
| Scope: |
"The client DOES support the electronic business card format (vCard)" |
| Text: |
When a WAE user agent accesses vcard content it must be able
to display the TELEPHONE NUMBER property. [Wireless Application Environment Specification section 6.7.2] |
| Note: |
Get the user to access a vCard with a known TELEPHONE NUMBER
property from the device under test. Make sure that the value in the
TELEPHONE NUMNER property is displayed. |
|
| ID: |
wae2/media/vcard/cardrules/5 |
| Class: |
D |
| Scope: |
"The client DOES support transmission of electronic business cards (vCard)" |
| Text: |
When a WAE user agent exchanges a vcard it must include the
NAME property. [Wireless Application Environment Specification section 6.7.2] |
| Note: |
It is not defined how a user agent actually exchanges vcards.
All of our test suits are based on HTTP communication. |
|
| ID: |
wae2/media/vcard/cardrules/6 |
| Class: |
D |
| Scope: |
"The client DOES support transmission of electronic business cards (vCard)" |
| Text: |
When a WAE user agent exchanges a vcard it must include the
TELEPHONE NUMBER property. [Wireless Application Environment Specification section 6.7.2] |
| Note: |
It is not defined how a user agent actually exchanges vcards.
All of our test suits are based on HTTP communication. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
| ID: |
wae2/media/vcal/calrules/1 |
| Class: |
C |
| Scope: |
"The client DOES support internet calendaring and scheduling core object (vCalendar)" |
| Text: |
When a user agent supports vCalendar exchange through WSP
and W-HTTP it must support the 'text/x-vCalendar' MIME type. [Wireless Application Environment Specification section 6.8.2] |
| Note: |
Get the user to select a link that loads content with the
MIME type 'text/x-vCalendar' and the extension '.vcs'. Make sure that
the user agent does not display the error that the MIME type is not
supported. We could also make sure that the user agent declares the
'text/x-vCalendar' type in its accept header, but this would not
actually check that it does support it, just that it claims to. |
|
| ID: |
wae2/media/vcal/calrules/2 |
| Class: |
D |
| Scope: |
"The client DOES support internet calendaring and scheduling core object (vCalendar)" |
| Text: |
When a user agent supports vCalendar exchange through WDP
it must support vCalendar on the port assigned in WDP
(unsecure : 9205, secure : 9207). [Wireless Application Environment Specification section 6.8.2] |
| Note: |
Untestable as we can not support direct communication with
clients using WDP datagrams. All of our test suits are based on HTTP
communication. |
|
| ID: |
wae2/media/vcal/calrules/3 |
| Class: |
C |
| Scope: |
"The client DOES support internet calendaring and scheduling core object (vCalendar)" |
| Text: |
When a WAE user agent accesses vCalendar content it must be
able to display the vEvent object to the user. [Wireless Application Environment Specification section 6.7.2] |
| Note: |
Get the user to access a vCalendar with known values using
the device under test. Make sure that the vEvent object is displayed. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
| ID: |
wae2/media/multipart/form/1 |
| Class: |
A |
| Text: |
A WAE user agent must support multipart messages returning
a set of values from a form. [Wireless Application Environment Specification section 6.9.5] |
| Note: |
Create a document that contains a form, and submit this form
as multipart/form-data. Make sure that the data submitted is of
multipart/form-data form. |
|
| ID: |
wae2/media/multipart/form/2 |
| Class: |
D |
| Scope: |
"The client DOES support WSP" |
| Text: |
When a WAE user agent supports WSP it must be able to submit
form data in 'application/vnd.wap.multipart.form-data'. [Wireless Application Environment Specification section 6.9.5] |
| Note: |
This is untestable as we can't tell what is being sent to the
gateway, only what is sent from the gateway to the origin server.
Therefore we can't make sure that the client is sending
'application/vnd.wap.multipart.form-data'. We could however test to just
make sure that an error does not occur when the device tries to send
this type. This would not test to make sure that the content has
actually been sent as 'application/vnd.wap.multipart.form-data' however. |
|
| ID: |
wae2/media/multipart/form/3 |
| Class: |
C |
| Scope: |
"The client DOES W-HTTP" |
| Text: |
When a WAE user agent supports W-HTTP it must be able to
submit form data in 'multipart/form-data'. [Wireless Application Environment Specification section 6.9.5] |
| Note: |
Create a document that contains a form. Make sure that the
data submitted by the user agent is of 'multipart/form-data' form. |
|
| ID: |
wae2/media/multipart/form/4 |
| Class: |
C |
| Scope: |
"The proxy DOES support multipart messages and WSP" |
| Text: |
When a WAP proxy supports WSP it must be able to convert
'application/vnd.wap.multipart.form-data' into 'multipart/form-data'. [Wireless Application Environment Specification section 6.9.5] |
| Note: |
Create a document that has a form on it and submits it as a
'application/vnd.wap.multipart.form-data' document. Check the
content-type header when the document is sent to the origin server to
make sure that it is now 'multipart/form-data'. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
| ID: |
wae2/features/interface/protocol/protorules/1 |
| Class: |
B |
| Text: |
WAE user agents must support the Hypermedia Transfer Service. [Wireless Application Environment Specification section 7.1.1.2] |
| Note: |
We cannot be sure that the request is sent through a WAP proxy
and not direct to the origin server. We have no defined WAP proxy. |
|
| ID: |
wae2/features/interface/protocol/protorules/2 |
| Class: |
B |
| Text: |
WAP proxies must support the Hypermedia Transfer Service. [Wireless Application Environment Specification section 7.1.1.2] |
| Note: |
We cannot be sure that the request is sent through a WAP proxy
and not direct to the origin server. We have no defined WAP proxy. |
|
| ID: |
wae2/features/interface/protocol/protorules/3 |
| Class: |
B |
| Text: |
WAE user agents must support WSP or HTTP. [Wireless Application Environment Specification section 7.1.1.2] |
| Note: |
[NCC]:{ A pre-defined WSP transaction could easily be
verified by the Protocol test tools. Currently the Protocol Test Tools
do not support W-HTTP. The method of testing for HTTP which is
suggested above is essentially to monitor all traffic and ensure that
there is no WSP from the DUT, so that use of HTTP can be assumed. The
Protocol Test Tools are based on a Relay approach: a DUT will send WSP
traffic direct to the test tools which will then forward it to the
intended recipient. The Protocol Test Tools do not support W-HTTP
(only WSP) so cannot be used for the suggested test.} |
|
| ID: |
wae2/features/interface/protocol/protorules/4 |
| Class: |
B |
| Text: |
WAP proxies must support WSP or HTTP. [Wireless Application Environment Specification section 7.1.1.2] |
| Note: |
[NCC]:{ A pre-defined WSP transaction could easily be
verified by the Protocol test tools. Currently the Protocol Test Tools
do not support W-HTTP. The method of testing for HTTP which is
suggested above is essentially to monitor all traffic and ensure that
there is no WSP from the DUT, so that use of HTTP can be assumed. The
Protocol Test Tools are based on a Relay approach: a DUT will send WSP
traffic direct to the test tools which will then forward it to the
intended recipient. The Protocol Test Tools do not support W-HTTP
(only WSP) so cannot be used for the suggested test.} |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
| ID: |
wae2/features/interface/cache/cacherules/1 |
| Class: |
B |
| Text: |
WAE user agents must support the caching model. [Wireless Application Environment Specification section 7.1.2.2] |
| Note: |
This is marked as untestable as assertions for this need to
come from the caching model specification. This however is not being
tested in the VSWAP June 2001 release. |
|
There are no testable assertions in this section.
| ID: |
wae2/features/interface/header/1 |
| Class: |
B |
| Text: |
When a request is made by the WAE user agent, the request
headers in each request during the lifetime of the session must be
combined with the cached request headers before the request header
information is used. [Wireless Application Environment Specification section 7.1.4] |
| Note: |
Untestable as we cannot ensure that the content of the request
header information is from the client or whether the gateway has affected
the content. |
|
| ID: |
wae2/features/interface/header/2 |
| Class: |
B |
| Text: |
When a request header is present in a request, any cached
request headers with the same name must not be taken into account
during the processing of the method invocation. [Wireless Application Environment Specification section 7.1.4] |
| Note: |
Untestable as we cannot ensure that the content of the request
header information is from the client or whether the gateway has affected
the content. |
|
| ID: |
wae2/features/interface/header/3 |
| Class: |
B |
| Text: |
Client headers that the user agent sends as part of the resume
service primitive of the WSP layer must be used to update the cached
request headers. [Wireless Application Environment Specification section 7.1.4] |
| Note: |
Untestable as we cannot ensure that the content of the request
header information is from the client or whether the gateway has affected
the content. |
|
| ID: |
wae2/features/interface/header/4 |
| Class: |
B |
| Text: |
Client headers that the user agent sends as part of the
connect service primitive of the WSP layer must be used to update the
cached request headers. [Wireless Application Environment Specification section 7.1.4] |
| Note: |
Untestable as we cannot ensure that the content of the request
header information is from the client or whether the gateway has affected
the content. |
|
| ID: |
wae2/features/uri/1 |
| Class: |
A |
| Text: |
A WAE user agent must be able to handle a URI of at least
1024 octets. [Wireless Application Environment Specification section 7.2] |
| Note: |
Create a link in a WML2 document that is 1024 octets in length.
Make sure that the resource is loaded. This test relies on the gateway
also correctly supporting uris of at least 1024 octets. |
|
| ID: |
wae2/features/uri/2 |
| Class: |
A |
| Text: |
A WAP proxy must be able to handle a URI of at least
1024 octets. [Wireless Application Environment Specification section 7.2] |
| Note: |
Create a link in a WML2 document that is 1024 octets in length.
Make sure that the resource is loaded. This test relies on the client
also correctly supporting uris of at least 1024 octets. |
|
| ID: |
wae2/features/uri/http/1 |
| Class: |
B |
| Text: |
When a WAE user agent retrieves a resource specified by the
HTTP URI scheme, it must communicate with the proxy or origin server
using wireless profiled HTTP and/or WSP. [Wireless Application Environment Specification section 7.2.1] |
| Note: |
This is untestable as we can't see what protocol is/are being
used from the application layer. |
|
| ID: |
wae2/features/uri/https/1 |
| Class: |
B |
| Text: |
When a WAE user agent retrieves a resource specified by the
HTTPS URI scheme using the connection-oriented protocol stack, it must
use wireless profiled HTTP over the transport layer security protocol
in accordance with 'WAP TLS' to communicate with the origin server. [Wireless Application Environment Specification section 7.2.2] |
| Note: |
This is untestable as we can't see what protocol is/are being
used from the application layer. |
|
| ID: |
wae2/features/uri/https/2 |
| Class: |
B |
| Text: |
When a WAE user agent retrieves a resource specified by the
HTTPS URI scheme using the connection-oriented protocol stack and does
not use wireless profiled HTTP over the transport layer security
protocol in accordance with 'WAP TLS' to communicate with the origin
server an indication of lack of security must be given to the user,
and the retrieval attempt must be aborted. [Wireless Application Environment Specification section 7.2.2] |
| Note: |
This is untestable as we can't set up this situation. |
|
| ID: |
wae2/features/uri/https/3 |
| Class: |
B |
| Text: |
The user agent must use the HTTP CONNECT method to establish
a secure transport protocol tunnel with the origin server. [Wireless Application Environment Specification section 7.2.2] |
| Note: |
This is untestable as we can't tell what connect method the
device is using from the application layer. |
|
|
| ID: |
wae2/features/uri/https/5 |
| Class: |
B |
| Text: |
When a user agent requests a resource by the HTTPS URI using
the datagram-orientated protocol stack, consisting of WDP, WTP + WSP
with WTLS, it must request the resource via WSP using a WTLS secured
session. [Wireless Application Environment Specification section 7.2.2] |
| Note: |
This is untestable as we can't set this situation up or see
what protocols are being used from the application level. |
|
| ID: |
wae2/features/uri/https/6 |
| Class: |
B |
| Text: |
When a user agent requests a resource requiring a WTLS
session, it must give an indication to the user, and abort the
retrieval if the WTLS session can not be set up. [Wireless Application Environment Specification section 7.2.2] |
| Note: |
This is untestable as we can't set this situation. |
|
| ID: |
wae2/features/uri/https/7 |
| Class: |
B |
| Text: |
When a user agent requests a resource by an HTTPS URI using
the connection-oriented protocol through a WAP proxy, the WAP proxy
must use HTTP/1.1 over TLS or SSL to communicate with the origin server. [Wireless Application Environment Specification section 7.2.2] |
| Note: |
This is untestable as we can't set this situation up. |
|
|
|
| ID: |
wae2/features/uri/https/10 |
| Class: |
B |
| Text: |
When a wap proxy mediating a resource specified by the
HTTPS URI scheme can not establish a secure connection it must report
an error by using the HTTP status code 502 "Bad Gateway". [Wireless Application Environment Specification section 7.2.2] |
| Note: |
This is untestable as we can't set this situation up. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
|
| ID: |
wae2/features/push/pushrules/2 |
| Class: |
D |
| Scope: |
"The client DOES support PUSH" |
| Text: |
When a user agent supports push it must support the Service
Indication. [Wireless Application Environment Specification section 7.3.2] |
| Note: |
This is marked as untestable as this is thoroughly tested in
the push service indication assertion specification. |
|
| ID: |
wae2/features/push/pushrules/3 |
| Class: |
D |
| Scope: |
"The client DOES support PUSH" |
| Text: |
When a user agent supports push over WSP, it must support
application/vnd.wap.multipart.mixed. [Wireless Application Environment Specification section 7.3.2] |
| Note: |
This is marked as untestable as there is no definition or
reference as to how the device must support this type. |
|
| ID: |
wae2/features/push/pushrules/4 |
| Class: |
D |
| Scope: |
"The client DOES support PUSH" |
| Text: |
When a user agent supports push over W-HTTP, it must support
multipart/mixed. [Wireless Application Environment Specification section 7.3.2] |
| Note: |
This is marked as untestable as there is no definition or
reference as to how the device must support this type. |
|
| ID: |
wae2/features/push/pushrules/5 |
| Class: |
D |
| Scope: |
"The client DOES support PUSH" |
| Text: |
When a user agent supports push over WSP, it must support
application/vnd.wap.multipart.related. [Wireless Application Environment Specification section 7.3.2] |
| Note: |
This is marked as untestable as there is no definition or
reference as to how the device must support this type. |
|
| ID: |
wae2/features/push/pushrules/6 |
| Class: |
D |
| Scope: |
"The client DOES support PUSH" |
| Text: |
When a user agent supports push over W-HTTP, it must support
multipart/related. [Wireless Application Environment Specification section 7.3.2] |
| Note: |
This is marked as untestable as there is no definition or
reference as to how the device must support this type. |
|
| ID: |
wae2/features/push/pushrules/7 |
| Class: |
D |
| Scope: |
"The client DOES support PUSH" |
| Text: |
When a user agent supports push over WSP, it must support
application/vnd.wap.multipart.alternative. [Wireless Application Environment Specification section 7.3.2] |
| Note: |
This is marked as untestable as there is no definition or
reference as to how the device must support this type. |
|
| ID: |
wae2/features/push/pushrules/8 |
| Class: |
D |
| Scope: |
"The client DOES support PUSH" |
| Text: |
When a user agent supports push over W-HTTP, it must support
multipart/alternative. [Wireless Application Environment Specification section 7.3.2] |
| Note: |
This is marked as untestable as there is no definition or
reference as to how the device must support this type. |
|
| ID: |
wae2/features/push/pushrules/9 |
| Class: |
D |
| Scope: |
"The client DOES support PUSH" |
| Text: |
When a user agent supports Push it must support the Push
Message format. [Wireless Application Environment Specification section 7.3.2] |
| Note: |
This is marked as untestable as this is thoroughly tested in
the push specification. |
|
There are no testable assertions in this section.
| ID: |
wae2/features/internationalisation/encoding/1 |
| Class: |
A |
| Text: |
A WAE user agent must support UTF-8 character encoding. [Wireless Application Environment Specification section 7.4.1] |
| Note: |
Get the user to access a link of a document that is encoded in
UTF-8. Make sure that the document is displayed correctly. |
|
| ID: |
wae2/features/internationalisation/encoding/2 |
| Class: |
A |
| Text: |
A WAE user agent must support UTF-16 character encoding. [Wireless Application Environment Specification section 7.4.1] |
| Note: |
Get the user to access a link of a document that is encoded
in UTF-16. Make sure that the document is displayed correctly. |
|
| ID: |
wae2/features/internationalisation/encoding/3 |
| Class: |
A |
| Text: |
A WAP proxy must support UTF-8 character encoding. [Wireless Application Environment Specification section 7.4.1] |
| Note: |
Get the user to access a link of a document that is encoded in
UTF-8. Make sure that the document is displayed correctly. |
|
| ID: |
wae2/features/internationalisation/encoding/4 |
| Class: |
A |
| Text: |
A WAP proxy must support UTF-16 character encoding. [Wireless Application Environment Specification section 7.4.1] |
| Note: |
Get the user to access a link of a document that is encoded
in UTF-16. Make sure that the document is displayed correctly. |
|
| ID: |
wae2/features/internationalisation/encoding/5 |
| Class: |
A |
| Text: |
When an XML document includes unknown characters (not as
specified in [RFC3023]), the WAP proxy or the user agent must inform
the user of the error. [Wireless Application Environment Specification section 7.4.1] |
| Note: |
Get the user to access a document that contains invalid XML.
Make sure that an error is displayed to the user. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
| ID: |
wae2/features/characteristics/headers/1 |
| Class: |
D |
| Scope: |
"The client advertises its supported media types in its 'accept' request header" |
| Text: |
When a user agent wants to advertise its media type support
it must do so in its 'Accept' request header. [Wireless Application Environment Specification section 7.5.1] |
| Note: |
Untestable as use of accept headers can be tailored by the user
agent based on context. |
|
| ID: |
wae2/features/characteristics/headers/2 |
| Class: |
D |
| Scope: |
"The client advertises its supported character encoding in its 'accept-charset' request header" |
| Text: |
When a user agent wants to advertise its character encoding
support it must do so in its 'Accept-Charset' request header. [Wireless Application Environment Specification section 7.5.1] |
| Note: |
Untestable as use of accept headers can be tailored by the user
agent based on context. |
|
| ID: |
wae2/features/characteristics/headers/3 |
| Class: |
D |
| Scope: |
"The client advertises its supported content-codings in its 'accept-encoding' request header" |
| Text: |
When a user agent wants to advertise its content-codings
support it must do so in its 'Accept-Encoding' request header. [Wireless Application Environment Specification section 7.5.1] |
| Note: |
Untestable as use of accept headers can be tailored by the user
agent based on context. |
|
| ID: |
wae2/features/characteristics/headers/4 |
| Class: |
D |
| Scope: |
"The client advertises its supported languages in its 'accept-language' request header" |
| Text: |
When a user agent wants to advertise its language support it
must do so in its 'Accept-Language' request header. [Wireless Application Environment Specification section 7.5.1] |
| Note: |
Untestable as use of accept headers can be tailored by the user
agent based on context. |
|
| ID: |
wae2/features/characteristics/headers/5 |
| Class: |
B |
| Text: |
When a WAP proxy receives a document, it must assume the value
of Accept, Accept-Charset, Accept-Encoding and Accept-Language headers as
defined in [HTTP/1.1]. [Wireless Application Environment Specification section 7.5.1] |
| Note: |
Untestable as use of accept headers can be tailored by the user
agent based on context. |
|
| ID: |
wae2/features/characteristics/headers/6 |
| Class: |
B |
| Text: |
When a WAP proxy transmits content it must do so without
changing the media type when the WAE user agent prefers the original
media type. [Wireless Application Environment Specification section 7.5.1] |
| Note: |
This is untestable as the headers the client transmits can not
be seen at the origin server. Only the headers sent by the proxy can be
seen. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
| ID: |
wae2/features/control/authentication/1 |
| Class: |
A |
| Text: |
User agents must implement HTTP/1.1 basic authentication. [Wireless Application Environment Specification section 7.10.1] |
| Note: |
Get the user to access a document that is protected by HTTP/1.1
authentication. Make sure that the user has to enter a username and
password to be able to navigate to the document. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
| ID: |
wae2/features/control/crypto/cryptorule/1 |
| Class: |
A |
| Text: |
A WAP Proxy agent must be able to compile a script compilation
unit that refers to the Crypto library. [Wireless Application Environment Specification section 7.10.3.2] |
| Note: |
Get the user to load a document that contains a WMLScript that
contains a crypto library function. Make sure that the document is
displayed correctly with no errors. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
|
| ID: |
wae2/wbmp/typeid/2 |
| Class: |
C |
| Scope: |
"The client DOES support graphical images" |
| Text: |
When a user agent supports WBMP, it must report all supported
WBMP types in the HTTP/WSP accept request header. [Wireless Application Environment Defined Media Type Specification section 4.1] |
| Note: |
In the setup of the test session ask the user what WBMP types
the device supports. Then get the user agent to access a document. Make
sure that the 'accept' header contains the same media types as declared
in the setup of the test session. |
|
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.
There are no testable assertions in this section.