Related Tips & Info

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

MigrationDeletedUser
0 Likes

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
Comment List
Related
Recommended

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.