Hi.

On 2/24/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:Should have looked
more closely; it's obvious to me that it's a locale
issue. Need to use explcit locale in the tests.



Yes, indeed. The tests are locale specific. It's testing for a locale
dependant formated decimal number.
Because I'm running a german windows the output is "22,70"and not the
expected "22.70".


But now I have some other strange test results.

Failed tests:
 org.apache.tapestry.integration.IntegrationTests.password_field(
org.apache.tapestry.integration.IntegrationTests.password_field)
org.apache.tapestry.corelib.components.OutputTest.simple_output(
org.apache.tapestry.corelib.components.OutputTest.simple_output)
org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
(
org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
)

The OutputTest tests fail because of the locale settings. OK.

But the other ones show a strange behaviour.

The IntegrationTests.password_field test does not allways fail - only
sometime. Seems like a timing problem?

The ClasspathAssetAliasManagerImplTest test only fail if they are run from
maven!?
If I start them with "mvn test" (on the command line or with the Eclipse
Maven plugin) they fail.
If I start the tests with the TestNG Eclipse plugin they do not fail.

Anyone else seeing similliar effects?

BTW
How can I debug the tests with Eclipse while running from the Eclipse Maven
plugin?

--
og

Reply via email to