W3C home > Mailing lists > Public > www-tag@w3.org > January 2002

Is 'testability' a useful architectural constraint?

From: Chris Lilley <chris@w3.org>
Date: Mon, 7 Jan 2002 16:51:07 +0100
Message-ID: <491340808761.20020107165107@w3.org>
To: www-tag@w3.org
Having examined simplicity, it strikes me that testability is another
desirable feature. One thing that the QA activity has shown is that
good specs have testable assertions, and conformance criteria, and
test suites. This makes implementation reports and maturity assesment
much easier, and if the working group is involved in the creation,
discussion and bugfixing of the test suite then the overal quality of
the spec also seems to benefit.

If a spec is not testable and conformance cannot be assesed, it makes
it hard for other specs to interact with it in consistent and useful
ways. It can also show that the working group thinks it has consensus
on what the spec does, but is wrong ;-)

Thus, testability aids clean architecture.

-- 
 Chris                          mailto:chris@w3.org
Received on Monday, 7 January 2002 10:51:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:03 GMT