Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Why, after upgrading to SilkCentral Test Manager 2008, do my JUnit tests exit with the status of "Not Executed"?

Why, after upgrading to SilkCentral Test Manager 2008, do my JUnit tests exit with the status of "Not Executed"?

Problem:

Why, after upgrading to SilkCentral Test Manager 2008, do my JUnit tests exit with the status of "Not Executed"?

Resolution:

After executing the JUnit tests, inspect the results and under the messages tab verify if the following error message is displayed:

junit error

If the above error has occurred it is because the classpath you specified for the Test Definition properties contains the period symbol in either of the following formats:

  • ".;" if specified before the end of the classpath
  • "." if specified at the end of the classpath

To resolve this issue simply follow the period symbol with a backslash:

  • ".\;"
  • ".\"

Old KB# 25037

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:51
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.