Re: [Userops] Userops Acid Test v0.1

[Christopher Allan Webber]

Asheesh Laroia writes:

> On Sun, Sep 27, 2015 at 9:20 AM, Christopher Allan Webber <
> address@hidden> wrote:
>
>> Hello all,
>>
>> I thought it would be useful for me to write up, in an
>> implementation-agnostic form, a clear example of what I think
>> (personally) are a set of useful requirements for a Userops type system.
>> So here's a braindump of what I see are essential properties of such a
>> system...
>>
>>   http://dustycloud.org/blog/userops-acid-test/
>>
>> I wrote this up independently, and I'm sure I'm missing some things.
>> Consider this Userops Acid Test v0.1?
>>
>
> FWIW the original Acid Test gives users a very quick binary: The thing
> looks visually correct, or it doesn't.
>
> You can look at http://acid2.acidtests.org/#top and
> http://www.w3.org/Style/CSS/Test/CSS1/current/test5526c.htm to get a sense
> of that.
>
> So I propose that a userops Acid Test should have a boolean answer, even if
> the answer ends up being "No for a stupid reason" for one system or
> another. We can all live with that. I think this was an issue with Acid
> Test 1, but I think that everyone lived with it.

It took me half a month to reply to this (eek!) but I agree, "acid test"
was probably not a good name choice... this is not a very good pass/fail
type test.  It's something that involves a bit more subjective ranking.

Which is probably still useful, but probably not something that should
be called "acid test"!