Unit test error - NumberFormatException on duration time


I have created a new TestSuite.
It has a single unit test which tests a easy addInts function.

When I try to run the test suite with the single unit test I get an error that seems to be about the duration of the unit test run.

This is my error :

and this is the console output :

As you can see the number written in the number format exception is exactly the duration of the test suite run.

Have you any ideas on how could I fix it?

Thanks a lot in advance

wMTestSuite is meant to test only with static values which you captured during your happy, failure path of your flow service. Dynamic values such as runtime datetime or any dynamic database values should not to be validated using the TestSuites.

if you can introduce the condition in your testcase to exclude these variables not to be tested during the wMTest execution using xPath.


Check the locale settings for the run-time environments. Seems to be a mismatch somewhere between expecting ‘.’ vs. ‘,’ as the decimal separator.

1 Like

Hi reamon,

where can I modify the locale settings for the run-time environment?

Thanks a lot,

It’s been a while since I worked with WmUnit but as I recall, when running the tests in Designer, the test runner is local to your machine which calls the services on the IS server. The locale of your Designer environment likely needs to match the locale of the IS instance.

But that’s just a guess on my part. Perhaps others have additional info and may be able to confirm or dismiss that differing locale settings could be the issue.

This would be a defect. I don’t see any quick workaround by specifying or updating the locale in the Designer.

Except, if you agree to temporarily set your Windows system locale to US and try it out.
For reference: change system locale …

Feel free to create a service incident. In any case, this has to be addressed through product fixes.

1 Like


I have tryed changing the Locale to “ENG (United States) but I still have the error about the duration”


Hi - Fix for this issue was made public for most of the released versions. You might want to install and try.
-Thanks, Sanjib

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.