- From: Shane P. McCarron <shane@aptest.com>
- Date: Wed, 13 Dec 2000 18:26:18 -0600
- To: Ian Hickson <ian@hixie.ch>
- CC: Karl Dubost <karl@w3.org>, www-html-testsuite@w3.org
At ApTest, our position is that you specify all assertions in the
specification for the test, even if some are marked as class B
(untestable) or class D (optional and untestable). Those just get left
out of test sessions when they are created.
Ian Hickson wrote:
>
> On Wed, 13 Dec 2000, Shane P. McCarron wrote:
> >
> > As assertion is a active voice, present tense, minimal boolean statement
> > that evaluates to true when an implementation adheres to the behavior
> > specified. An example might be "The implementation shall accept
> > documents that have neither a BODY start nor a BODY end tag." This is
> > an HTML 3.2 assertion.
>
> A similar term is "testable statement". Not all assertions are testable.
> An example of an untestable assertion is "Conforming user agents must
> correctly map to ISO 10646 all characters in any character encodings that
> they recognize (or they must behave as if they did)." (HTML4:5.2.1)
>
> For writing a test suite, the important statements are the testable
> statements.
>
> --
> Ian Hickson )\ _. - ._.) fL
> Netscape, Standards Compliance QA /. `- ' ( `--'
> +1 650 937 6593 `- , ) - > ) \
> irc.mozilla.org:Hixie _________________________ (.' \) (.' -' __________
--
Shane P. McCarron phone: +1 763 786-8160
ApTest fax: +1 763 786-8180
mobile: +1 612 799-6942
e-mail: shane@aptest.com
Received on Wednesday, 13 December 2000 19:26:58 UTC