[Seaside-dev] Issue 292 in seaside: Remove WAGemStoneMock* classes from Seaside-Tests-Core

codesite-noreply at google.com codesite-noreply at google.com
Thu Jan 22 15:29:38 UTC 2009


Comment #7 on issue 292 by WeybridgeWay: Remove WAGemStoneMock* classes  
from Seaside-Tests-Core
http://code.google.com/p/seaside/issues/detail?id=292

I'm happy to undo the changes, but I'm not sure what we are trying to test.  
Are streams supposed to trigger an
exception on #next? I don't think that is ANSI (though I've been wrong  
recently!). In another issue we seemed to
come to an agreement to check for #atEnd before sending #next. --James  
Foster

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings


More information about the seaside-dev mailing list