W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: CfC: WebApps testing process; deadline April 20

From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Tue, 19 Apr 2011 08:16:45 -0700
Message-ID: <BANLkTikv8Dg4mo61fXKSQfyztxLRHAym2w@mail.gmail.com>
To: Arthur Barstow <art.barstow@nokia.com>
Cc: ext Aryeh Gregor <Simetrical+w3c@gmail.com>, public-webapps <public-webapps@w3.org>
On 4/19/11, Arthur Barstow <art.barstow@nokia.com> wrote:
> On Apr/18/2011 12:29 PM, ext Aryeh Gregor wrote:
>> On Sun, Apr 17, 2011 at 9:38 PM, Garrett Smith<dhtmlkitchen@gmail.com>
>> wrote:
>>> The superfluous, badly worded maladvice remains: "Within each test one
>>> may have a number of asserts."
>>> Awkward wording to explicitly mention that such bad practice is allowed.
>> I'll reiterate that I think multiple asserts per test are useful, and
>> have seen no substantive arguments to the contrary.  It's true that
>> the sentence would be better worded as "Each test can have a number of
>> asserts."
> Again, I don't think we should be overly constraining here. I changed
> that bullet to:
> [[
> * Each test can have one or more asserts. Note: some prefer a test is
> limited to a single assertion but that is not mandatory.
> ]]
Superfluous. And by that I mean unnecessary/needless. Why? Because if
the author doesn't seeing the harm in multiple assertions, he['ll add
them; he will do that anyway.

Eschew surplusage.
Received on Tuesday, 19 April 2011 15:17:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:19 UTC