You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karen Lease (JIRA)" <ji...@codehaus.org> on 2010/06/18 23:33:12 UTC
[jira] Created: (SUREFIRE-625) Testclass which fails during launch
claims to have no tests
Testclass which fails during launch claims to have no tests
-----------------------------------------------------------
Key: SUREFIRE-625
URL: http://jira.codehaus.org/browse/SUREFIRE-625
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 2.5
Environment: Maven version: 2.0.10 (surefire 2.5)
Java version: 1.6.0_15
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Reporter: Karen Lease
Priority: Minor
Attachments: surefire_junit4.8.1_issue.zip
I have a test which fails during launch due to this exception:
bq.java.lang.SecurityException: class ";com.spx.messageservice.MessageServiceException"'s signer information does not match signer information of other classes in the same package
This happened because the class under test depends on some other classes in the same package in a signed jar.
The problem is that using our normal maven environment, this error is not shown at all. Instead the surefire report for this class contained the results from the previous test in the module!
If the test is run by itself with mvn -Dtest=TestClass, then maven says there are no tests run and no errors!
If I use junit 4.8.1 in my pom file, I get this output on the console and in the surefire .txt report:
bq.Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
The XML surefire report is not produced at all.
If I use junit 4.6 in my pom file, I get this output:
{quote}
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.047 sec <<< FAILURE!
initializationError(com.spx.messageservice.BusinessEventRegistrarTest) Time elapsed: 0 sec <<< ERROR!
java.lang.SecurityException: class "com.spx.messageservice.MessageServiceException"'s signer information does not match signer information of other classes in the same package
at java.lang.ClassLoader.checkCerts(ClassLoader.java:776)
...
{quote}
Both the .txt & .xml version of the surefire reports are produced.
After some experiments, I found that this happens for any junit version > 4.6.
If I run the test class with junit from the command line, both the 4.6 & 4.8.1 produce a stack trace showing the exception during launch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-625) Testclass which fails during launch
claims to have no tests
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated SUREFIRE-625:
----------------------------------------
Component/s: Junit 4.x support
> Testclass which fails during launch claims to have no tests
> -----------------------------------------------------------
>
> Key: SUREFIRE-625
> URL: http://jira.codehaus.org/browse/SUREFIRE-625
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Affects Versions: 2.5
> Environment: Maven version: 2.0.10 (surefire 2.5)
> Java version: 1.6.0_15
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Karen Lease
> Priority: Minor
> Attachments: surefire_junit4.8.1_issue.zip
>
>
> I have a test which fails during launch due to this exception:
> bq.java.lang.SecurityException: class ";com.spx.messageservice.MessageServiceException"'s signer information does not match signer information of other classes in the same package
> This happened because the class under test depends on some other classes in the same package in a signed jar.
> The problem is that using our normal maven environment, this error is not shown at all. Instead the surefire report for this class contained the results from the previous test in the module!
> If the test is run by itself with mvn -Dtest=TestClass, then maven says there are no tests run and no errors!
> If I use junit 4.8.1 in my pom file, I get this output on the console and in the surefire .txt report:
> bq.Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> The XML surefire report is not produced at all.
> If I use junit 4.6 in my pom file, I get this output:
> {quote}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.047 sec <<< FAILURE!
> initializationError(com.spx.messageservice.BusinessEventRegistrarTest) Time elapsed: 0 sec <<< ERROR!
> java.lang.SecurityException: class "com.spx.messageservice.MessageServiceException"'s signer information does not match signer information of other classes in the same package
> at java.lang.ClassLoader.checkCerts(ClassLoader.java:776)
> ...
> {quote}
> Both the .txt & .xml version of the surefire reports are produced.
> After some experiments, I found that this happens for any junit version > 4.6.
> If I run the test class with junit from the command line, both the 4.6 & 4.8.1 produce a stack trace showing the exception during launch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-625) Testclass which fails during launch
claims to have no tests
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-625.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.7.2
Assignee: Kristian Rosenvold
Fixed in r1058735
> Testclass which fails during launch claims to have no tests
> -----------------------------------------------------------
>
> Key: SUREFIRE-625
> URL: http://jira.codehaus.org/browse/SUREFIRE-625
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Affects Versions: 2.5
> Environment: Maven version: 2.0.10 (surefire 2.5)
> Java version: 1.6.0_15
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Karen Lease
> Assignee: Kristian Rosenvold
> Priority: Minor
> Fix For: 2.7.2
>
> Attachments: surefire_junit4.8.1_issue.zip
>
>
> I have a test which fails during launch due to this exception:
> bq.java.lang.SecurityException: class ";com.spx.messageservice.MessageServiceException"'s signer information does not match signer information of other classes in the same package
> This happened because the class under test depends on some other classes in the same package in a signed jar.
> The problem is that using our normal maven environment, this error is not shown at all. Instead the surefire report for this class contained the results from the previous test in the module!
> If the test is run by itself with mvn -Dtest=TestClass, then maven says there are no tests run and no errors!
> If I use junit 4.8.1 in my pom file, I get this output on the console and in the surefire .txt report:
> bq.Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> The XML surefire report is not produced at all.
> If I use junit 4.6 in my pom file, I get this output:
> {quote}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.047 sec <<< FAILURE!
> initializationError(com.spx.messageservice.BusinessEventRegistrarTest) Time elapsed: 0 sec <<< ERROR!
> java.lang.SecurityException: class "com.spx.messageservice.MessageServiceException"'s signer information does not match signer information of other classes in the same package
> at java.lang.ClassLoader.checkCerts(ClassLoader.java:776)
> ...
> {quote}
> Both the .txt & .xml version of the surefire reports are produced.
> After some experiments, I found that this happens for any junit version > 4.6.
> If I run the test class with junit from the command line, both the 4.6 & 4.8.1 produce a stack trace showing the exception during launch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira