[JBoss JIRA] Created: (ARQ-97) Load classes and resources from ShrinkWrap archive
by Dan Allen (JIRA)
Load classes and resources from ShrinkWrap archive
--------------------------------------------------
Key: ARQ-97
URL: https://jira.jboss.org/jira/browse/ARQ-97
Project: Arquillian
Issue Type: Bug
Components: Weld Containers
Affects Versions: 1.0.0.Alpha1
Reporter: Dan Allen
Fix For: 1.0.0.Alpha2
When the test, or libraries used by the test, attempt to load a class or resource from the classpath, that request should be diverted to look in the ShrinkWrap archive defined by the test. Currently, this classloading operation is looking in the classpath visible to the test runner. This causes two problems:
1. resources in the ShrinkWrap archive are not found
2. the classpath available to the test case is leaking (only resources in the ShrinkWrap archive should be visible)
The classpath needs to be constrained/protected.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (ARQ-181) When using @Text expected exception, the internal state of the TestResult is unknown
by Aslak Knutsen (JIRA)
When using @Text expected exception, the internal state of the TestResult is unknown
------------------------------------------------------------------------------------
Key: ARQ-181
URL: https://jira.jboss.org/browse/ARQ-181
Project: Arquillian
Issue Type: Bug
Components: Test Harness Integration
Reporter: Aslak Knutsen
When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not.
JUnit
@Test(expected=Exception.class)
TestNG
@Test(expectedException=Exception.class)
@ExpectedException(Exception.class)
Follow up with TestNG and JUnit to see how this can be done..
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (ARQ-191) Support the notion of shrinkwrap BundleArchive
by Thomas Diesler (JIRA)
Support the notion of shrinkwrap BundleArchive
-----------------------------------------------
Key: ARQ-191
URL: https://jira.jboss.org/browse/ARQ-191
Project: Arquillian
Issue Type: Task
Components: OSGi Integration
Reporter: Thomas Diesler
Currently we create test bundles like this
final JavaArchive archive = ShrinkWrap.create("test.jar", JavaArchive.class);
archive.setManifest(new Asset()
{
public InputStream openStream()
{
OSGiManifestBuilder builder = OSGiManifestBuilder.newInstance();
builder.addBundleSymbolicName(archive.getName());
builder.addBundleManifestVersion(2);
builder.addBundleActivator(SimpleActivator.class.getName());
// [TODO] generate a separate bundle the contains the test case
builder.addExportPackages(OSGiEmbeddedFrameworkTestCase.class);
builder.addImportPackages("org.jboss.arquillian.junit", "org.jboss.shrinkwrap.api", "org.jboss.shrinkwrap.api.spec");
builder.addImportPackages("javax.inject", "org.junit", "org.junit.runner");
return builder.openStream();
}
});
archive.addClasses(SimpleActivator.class, SimpleService.class);
archive.addClasses(OSGiEmbeddedFrameworkTestCase.class);
This should be done much easier via a BundleArchive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (ARQ-183) NPE in quickstart when not using profile
by Ondrej Žižka (JIRA)
NPE in quickstart when not using profile
----------------------------------------
Key: ARQ-183
URL: https://jira.jboss.org/browse/ARQ-183
Project: Arquillian
Issue Type: Bug
Affects Versions: 1.0.0.Alpha2
Reporter: Ondrej Žižka
Priority: Minor
NPE's are shame :-)
STR:
1) Follow http://docs.jboss.org/arquillian/reference/latest/en-US/html/gettingstart... up to the step `mvn -P...`, exclusive
2) Instead of that step, run `mvn` without profile
3) See the NPE:
-------------------------------------------------------------------------------
Test set: org.jboss.qa.eap.deployperfarq.TempConverterTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.019 sec <<< FAILURE!
initializationError(org.jboss.qa.eap.deployperfarq.TempConverterTest) Time elapsed: 0.004 sec <<< ERROR!
java.lang.NullPointerException
at org.jboss.arquillian.impl.DeployableTestBuilder.build(DeployableTestBuilder.java:82)
at org.jboss.arquillian.impl.DeployableTestBuilder.build(DeployableTestBuilder.java:71)
at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:68)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31)
at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24)
at org.apache.maven.surefire.junit4.JUnit4TestSet.<init>(JUnit4TestSet.java:45)
at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96)
at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209)
at org.apache.maven.surefire.Surefire.run(Surefire.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months