Linked by Thom Holwerda on Wed 26th Mar 2008 21:26 UTC, submitted by ohxten
Thread beginning with comment 306834
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2007-07-10
what is the point of the test, then?
ACID2 tested how to interpret even faulty code (how certain errors should be handled) - I assume ACID3 is the same.
Sure - one test can't possibly cover every quirk; and definitely doesn't dictate the behaviour of possibly related things, but if a 100% on the test does not guarantee what you are testing for (support of those standards), then it's not a very good test anyway.
Edited 2008-03-27 02:47 UTC