3:56 a.m.
TestNG not supported by Arquillian Service
------------------------------------------
Key: AS7-1303
URL: https://issues.jboss.org/browse/AS7-1303
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Final
Reporter: Aslak Knutsen
Assignee: Andrew Rubinger
Priority: Critical
Fix For: 7.0.1.Final
The Arquillian Service deployed during execution has a Deployment Processor hook to scan
for "Test Deployments" so it can lookup the Module etc during execution. This
scan assumes the TestDeployment will contain JUnits @RunWith annotation, which is true for
JUnit, but not so much for other test frameworks.
Arquillian is built to work with any test framework so TestNG/ScalaTest/Spock etc are all
valid targets.
Since the Arquillian Service is no longer a pre installed service, but deployed only
during test execution, it could make sense to remove the scanning(used to filter out test
deployment) and just consume all deployments during it's life time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:22 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1303) TestNG not supported by Arquillian Service
[
https://issues.jboss.org/browse/AS7-1303?page=com.atlassian.jira.plugin.s...
]
Andrew Rubinger commented on AS7-1303:
--------------------------------------
Discussion to be resolved:
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-August/003427.html
Right now the tests asserting the ARQ Managed Container is working is off by default.
TestNG not supported by Arquillian Service
------------------------------------------
Key: AS7-1303
URL: https://issues.jboss.org/browse/AS7-1303
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Final
Reporter: Aslak Knutsen
Assignee: Andrew Rubinger
Priority: Critical
Fix For: 7.0.1.Final
The Arquillian Service deployed during execution has a Deployment Processor hook to scan
for "Test Deployments" so it can lookup the Module etc during execution. This
scan assumes the TestDeployment will contain JUnits @RunWith annotation, which is true for
JUnit, but not so much for other test frameworks.
Arquillian is built to work with any test framework so TestNG/ScalaTest/Spock etc are all
valid targets.
Since the Arquillian Service is no longer a pre installed service, but deployed only
during test execution, it could make sense to remove the scanning(used to filter out test
deployment) and just consume all deployments during it's life time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:25 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (AS7-1303) TestNG not supported by Arquillian Service
[
https://issues.jboss.org/browse/AS7-1303?page=com.atlassian.jira.plugin.s...
]
Andrew Rubinger edited comment on AS7-1303 at 8/15/11 8:24 AM:
---------------------------------------------------------------
Discussion to be resolved:
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-August/003427.html
was (Author: ALRubinger):
Discussion to be resolved:
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-August/003427.html
Right now the tests asserting the ARQ Managed Container is working is off by default.
TestNG not supported by Arquillian Service
------------------------------------------
Key: AS7-1303
URL: https://issues.jboss.org/browse/AS7-1303
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Final
Reporter: Aslak Knutsen
Assignee: Andrew Rubinger
Priority: Critical
Fix For: 7.0.1.Final
The Arquillian Service deployed during execution has a Deployment Processor hook to scan
for "Test Deployments" so it can lookup the Module etc during execution. This
scan assumes the TestDeployment will contain JUnits @RunWith annotation, which is true for
JUnit, but not so much for other test frameworks.
Arquillian is built to work with any test framework so TestNG/ScalaTest/Spock etc are all
valid targets.
Since the Arquillian Service is no longer a pre installed service, but deployed only
during test execution, it could make sense to remove the scanning(used to filter out test
deployment) and just consume all deployments during it's life time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:28 a.m.
New subject: [JBoss JIRA] Updated: (AS7-1303) TestNG not supported by Arquillian Service
[
https://issues.jboss.org/browse/AS7-1303?page=com.atlassian.jira.plugin.s...
]
Andrew Rubinger updated AS7-1303:
---------------------------------
Comment: was deleted
(was: Discussion to be resolved:
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-August/003427.html)
TestNG not supported by Arquillian Service
------------------------------------------
Key: AS7-1303
URL: https://issues.jboss.org/browse/AS7-1303
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Final
Reporter: Aslak Knutsen
Assignee: Andrew Rubinger
Priority: Critical
Fix For: 7.0.1.Final
The Arquillian Service deployed during execution has a Deployment Processor hook to scan
for "Test Deployments" so it can lookup the Module etc during execution. This
scan assumes the TestDeployment will contain JUnits @RunWith annotation, which is true for
JUnit, but not so much for other test frameworks.
Arquillian is built to work with any test framework so TestNG/ScalaTest/Spock etc are all
valid targets.
Since the Arquillian Service is no longer a pre installed service, but deployed only
during test execution, it could make sense to remove the scanning(used to filter out test
deployment) and just consume all deployments during it's life time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:46 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1303) TestNG not supported by Arquillian Service
[
https://issues.jboss.org/browse/AS7-1303?page=com.atlassian.jira.plugin.s...
]
Andrew Rubinger commented on AS7-1303:
--------------------------------------
This is the deployment error received:
10:39:35,892 ERROR [org.jboss.msc.service] (MSC service thread 1-2) MSC00002: Invocation
of listener "org.jboss.as.arquillian.service.ArquillianService$1@4acf7fd0"
failed: java.lang.NoClassDefFoundError: org/junit/runner/RunWith
at
org.jboss.as.arquillian.service.ArquillianConfigBuilder.processDeployment(ArquillianConfigBuilder.java:56)
at
org.jboss.as.arquillian.service.ArquillianService$1.transition(ArquillianService.java:116)
at
org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1442)
at
org.jboss.msc.service.ServiceControllerImpl.access$2500(ServiceControllerImpl.java:49)
at
org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1940)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: java.lang.ClassNotFoundException: org.junit.runner.RunWith from [Module
"deployment.arquillian-service:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:330)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101)
... 9 more
TestNG not supported by Arquillian Service
------------------------------------------
Key: AS7-1303
URL: https://issues.jboss.org/browse/AS7-1303
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Final
Reporter: Aslak Knutsen
Assignee: Andrew Rubinger
Priority: Critical
Fix For: 7.0.1.Final
The Arquillian Service deployed during execution has a Deployment Processor hook to scan
for "Test Deployments" so it can lookup the Module etc during execution. This
scan assumes the TestDeployment will contain JUnits @RunWith annotation, which is true for
JUnit, but not so much for other test frameworks.
Arquillian is built to work with any test framework so TestNG/ScalaTest/Spock etc are all
valid targets.
Since the Arquillian Service is no longer a pre installed service, but deployed only
during test execution, it could make sense to remove the scanning(used to filter out test
deployment) and just consume all deployments during it's life time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:46 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (AS7-1303) TestNG not supported by Arquillian Service
[
https://issues.jboss.org/browse/AS7-1303?page=com.atlassian.jira.plugin.s...
]
Andrew Rubinger edited comment on AS7-1303 at 8/16/11 10:44 AM:
----------------------------------------------------------------
This is the deployment error received:
{code}10:39:35,892 ERROR [org.jboss.msc.service] (MSC service thread 1-2) MSC00002:
Invocation of listener
"org.jboss.as.arquillian.service.ArquillianService$1@4acf7fd0" failed:
java.lang.NoClassDefFoundError: org/junit/runner/RunWith
at
org.jboss.as.arquillian.service.ArquillianConfigBuilder.processDeployment(ArquillianConfigBuilder.java:56)
at
org.jboss.as.arquillian.service.ArquillianService$1.transition(ArquillianService.java:116)
at
org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1442)
at
org.jboss.msc.service.ServiceControllerImpl.access$2500(ServiceControllerImpl.java:49)
at
org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1940)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: java.lang.ClassNotFoundException: org.junit.runner.RunWith from [Module
"deployment.arquillian-service:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:330)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101)
... 9 more{code}
was (Author: ALRubinger):
This is the deployment error received:
10:39:35,892 ERROR [org.jboss.msc.service] (MSC service thread 1-2) MSC00002: Invocation
of listener "org.jboss.as.arquillian.service.ArquillianService$1@4acf7fd0"
failed: java.lang.NoClassDefFoundError: org/junit/runner/RunWith
at
org.jboss.as.arquillian.service.ArquillianConfigBuilder.processDeployment(ArquillianConfigBuilder.java:56)
at
org.jboss.as.arquillian.service.ArquillianService$1.transition(ArquillianService.java:116)
at
org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1442)
at
org.jboss.msc.service.ServiceControllerImpl.access$2500(ServiceControllerImpl.java:49)
at
org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1940)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: java.lang.ClassNotFoundException: org.junit.runner.RunWith from [Module
"deployment.arquillian-service:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:330)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101)
... 9 more
TestNG not supported by Arquillian Service
------------------------------------------
Key: AS7-1303
URL: https://issues.jboss.org/browse/AS7-1303
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Final
Reporter: Aslak Knutsen
Assignee: Andrew Rubinger
Priority: Critical
Fix For: 7.0.1.Final
The Arquillian Service deployed during execution has a Deployment Processor hook to scan
for "Test Deployments" so it can lookup the Module etc during execution. This
scan assumes the TestDeployment will contain JUnits @RunWith annotation, which is true for
JUnit, but not so much for other test frameworks.
Arquillian is built to work with any test framework so TestNG/ScalaTest/Spock etc are all
valid targets.
Since the Arquillian Service is no longer a pre installed service, but deployed only
during test execution, it could make sense to remove the scanning(used to filter out test
deployment) and just consume all deployments during it's life time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:34 a.m.
New subject: [JBoss JIRA] Updated: (AS7-1303) TestNG not supported by Arquillian Service
[
https://issues.jboss.org/browse/AS7-1303?page=com.atlassian.jira.plugin.s...
]
Andrew Rubinger updated AS7-1303:
---------------------------------
Priority: Blocker (was: Critical)
TestNG not supported by Arquillian Service
------------------------------------------
Key: AS7-1303
URL: https://issues.jboss.org/browse/AS7-1303
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Final
Reporter: Aslak Knutsen
Assignee: Andrew Rubinger
Priority: Blocker
Fix For: 7.0.1.Final
The Arquillian Service deployed during execution has a Deployment Processor hook to scan
for "Test Deployments" so it can lookup the Module etc during execution. This
scan assumes the TestDeployment will contain JUnits @RunWith annotation, which is true for
JUnit, but not so much for other test frameworks.
Arquillian is built to work with any test framework so TestNG/ScalaTest/Spock etc are all
valid targets.
Since the Arquillian Service is no longer a pre installed service, but deployed only
during test execution, it could make sense to remove the scanning(used to filter out test
deployment) and just consume all deployments during it's life time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:35 a.m.
New subject: [JBoss JIRA] Closed: (AS7-1303) TestNG not supported by Arquillian Service
[
https://issues.jboss.org/browse/AS7-1303?page=com.atlassian.jira.plugin.s...
]
Andrew Rubinger closed AS7-1303.
--------------------------------
TestNG not supported by Arquillian Service
------------------------------------------
Key: AS7-1303
URL: https://issues.jboss.org/browse/AS7-1303
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Final
Reporter: Aslak Knutsen
Assignee: Andrew Rubinger
Priority: Blocker
Fix For: 7.0.1.Final
The Arquillian Service deployed during execution has a Deployment Processor hook to scan
for "Test Deployments" so it can lookup the Module etc during execution. This
scan assumes the TestDeployment will contain JUnits @RunWith annotation, which is true for
JUnit, but not so much for other test frameworks.
Arquillian is built to work with any test framework so TestNG/ScalaTest/Spock etc are all
valid targets.
Since the Arquillian Service is no longer a pre installed service, but deployed only
during test execution, it could make sense to remove the scanning(used to filter out test
deployment) and just consume all deployments during it's life time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4833
days inactive
4870
days old
7 comments
2 participants
participants (2)
-
Andrew Rubinger (JIRA) -
Aslak Knutsen (JIRA)