[
https://issues.jboss.org/browse/ARQAJO-126?page=com.atlassian.jira.plugin...
]
Jan Papousek commented on ARQAJO-126:
-------------------------------------
Showcase [tests for
rich:autocomplete|https://github.com/richfaces/qa/blob/master/showcase-ft...]:
{code}
org.apache.maven.surefire.util.SurefireReflectionException:
java.lang.reflect.InvocationTargetException; nested exception is
java.lang.reflect.InvocationTargetException: null
java.lang.reflect.InvocationTargetException
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.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
Caused by: java.lang.ClassCastException: $Proxy25 cannot be cast to
org.jboss.arquillian.ajocado.framework.AjocadoConfiguration
at
org.jboss.arquillian.ajocado.framework.AjocadoConfigurationContext.getProxy(AjocadoConfigurationContext.java:32)
at
org.jboss.test.selenium.listener.FailureLoggingTestListener.onFailure(FailureLoggingTestListener.java:120)
at
org.jboss.test.selenium.listener.FailureLoggingTestListener.onTestFailure(FailureLoggingTestListener.java:75)
at org.testng.internal.Invoker.runTestListeners(Invoker.java:1884)
at org.testng.internal.Invoker.runTestListeners(Invoker.java:1868)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1279)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:758)
at org.testng.TestRunner.run(TestRunner.java:613)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:87)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1170)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1095)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:70)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:160)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:100)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
... 9 more
{code}
Test migration path for renaming Ajocado to Graphene
----------------------------------------------------
Key: ARQAJO-126
URL:
https://issues.jboss.org/browse/ARQAJO-126
Project: Arquillian Ajocado
Issue Type: Sub-task
Components: planning
Affects Versions: 1.0.0.CR2
Reporter: Lukáš Fryč
Assignee: Jan Papousek
Fix For: 1.0.0.CR3
Run any available tests (Metamer, RF Showcase, ...).
I have already checked that these are compilable,
but additionally we need to make sure that it's working at runtime.
Let's trigger several tests (not necessarily whole test suite) from each sample test
project.
Migration path:
* rename Maven groupIds to {{ajocado->graphene}}
* rename Maven artifactIds {{ajocado->graphene}}
* additionally {{arquillian-ajocado-junit}} was renamed to
{{arquillian-graphene-junit-container}} (ARQAJO-121)
* rename arquillian.xml configuration {{ajocado}} to {{graphene}}
* note: packages are not renamed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira