W3C home > Mailing lists > Public > public-css-testsuite@w3.org > August 2016

Test assertions requirement

From: Geoffrey Sneddon <me@gsnedders.com>
Date: Mon, 15 Aug 2016 23:18:11 +0100
To: www-style@w3.org
Message-ID: <9a43a91f-4f49-bf26-97ff-ac288778e9ee@gsnedders.com>
(Bcc'd public-css-testsuite; can we please keep responses on a single
mailing list, in this case www-style as it's about a WG resolution?)

In the SF F2F, 2016-05-09 we resolved:

RESOLVED: testharness.js tests don't need a meta assert (but reftests
still do)

>From memory, this was based on a mistaken understanding that assertions
were currently required everywhere.

This seems to contradict all documentation going back almost a decade!
In 2007 fantasai updated the wiki in
to state that assertions are optional (generically!).

I've been unable to find any discussion leading to this change, though
obviously discussion was happening around then (see
for example).

Do we want to revisit the resolution in light of being mistaken as to
previous policy? Or do we just want to consider the documentation wrong?

Received on Monday, 15 August 2016 22:18:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 20 January 2023 19:58:22 UTC