[Seaside-dev] Test failures in Pharo with current packages

Philippe Marschall philippe.marschall at gmail.com
Sat Jul 18 08:00:20 UTC 2009


2009/7/17 James Foster <Smalltalk at jgfoster.net>:
> Following is fairly typical (some fewer before and some fewer after):
>
> Loaded Seaside-Environment-lr.53.mcz
> Loaded Seaside-Tests-Environment-jf.14.mcz
>        668 run, 650 passes, 2 expected failures, 2 failures, 14 errors, 0
> unexpected passes
>                WAPlatformTest>>#testSeasideIntegerOnCharacter
>                WAEnvironmentDefaultHandlersTest>>#testAllTests
>                WAEnvironmentDefaultHandlersTest>>#testDefaultConfig
>                WAEnvironmentDefaultHandlersTest>>#testDefaultCounterDirect
>                WAEnvironmentDefaultHandlersTest>>#testDefaultCounterNavigate
>                WAEnvironmentDefaultHandlersTest>>#testDefaultTests
>                WASqueakPlatformTest>>#testConvertToSmalltalkNewlines
>                WASqueakPlatformTest>>#testSeasideIntegerOnCharacter
>                WAUtf8ResponseTest>>#testRedirectTo
>
>  WAEncoderSqueakTest>>#testEncodedSupplementaryMultilingualPlane
>
>  WAEncoderSqueakTest>>#testEncodedSupplementaryMultilingualPlaneUrl
>                WAEncoderSqueakTest>>#testEncodedUnicode
>                WAEncoderSqueakTest>>#testEncodedUnicodeUrl
>                WAUtf8UrlTest>>#testPrintString
>                WAEncoderSqueakTest>>#testLanguageTag
>                WAFileTest>>#testNonLatinWindowsPath

Is that with an up to date Pharo or with one that's some months old?

Cheers
Philippe


More information about the seaside-dev mailing list