[Seaside-dev] Issue 289 in seaside: Changes to Seaside-Tests-Core to address issues discovered in GemStone port

[codesite-noreply at google.com]

Status: Accepted
Owner: WeybridgeWay
Labels: Type-Portability Priority-Medium Version-Seaside2.9

New issue 289 by WeybridgeWay: Changes to Seaside-Tests-Core to address  
issues discovered in GemStone port
http://code.google.com/p/seaside/issues/detail?id=289

WACookieTest>>#testExpirePrinting creates a DateAndTime instance and  
expects it to be in GMT.
According to ANSI, the new instance will be in local time. If you want a  
specific time zone you need
to include the offset in the instance creation call. By  
specifying 'Duration zero' we get GMT.

WATestingFiles>>#samplePng appears to be excessively complex. It creates an  
Array, makes the
array mutable, puts something into the array, and then takes the thing out  
of the array. Because
GemStone does not allow making a static array mutable, this fails. It seems  
much simpler to just
return the thing that would have otherwise been put in the array.

--
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