<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Folks,<br>
<br>
the initial work on consolidating the arquillian test
infrastructure (<a href="https://issues.jboss.org/browse/AS7-734">AS7-734</a>)
is done. <br>
<br>
What you see in <a
href="https://github.com/jbossas/jboss-as/pull/49">pull request
49</a> installs the latest arquillian 1.0.0.Beta2 release to use
with all test suites. These are<br>
<br>
testsuite<br>
+ smoke<br>
+ spec<br>
+ integration<br>
<br>
The AS7 instance is started in managed mode (i.e. in a separate
VM). There is no arquillian subsystem any more nor any test
related jar artefacts in modules. Instead the arquillian endpoint
is deployed before the first test. As a side effect of arq managed
it is also possible to manually start up an AS7 instance and run
the tests as usual. This is useful for in container debugging. The
maven test goal works as expected. You can run individual tests
with -Dtest=Foo<br>
<br>
For this iteration, the focus was on infrastructure not on
individual test failures. All tests were ported to the new
arquillian API. Tests that failed for obvious reasons were fixed
the hard ones ignored.<br>
<br>
To see which tests were ignored run<br>
<br>
> git grep AS7-734<br>
<br>
Attached is a snapshot of the ignored tests. I'll take care of the
osgi ones. For the others I'd like to ask the respective authors
to have a look.<br>
<br>
JSF testing is currently disabled completely because of its
dependency on the arquillian servlet protocol. I'll follow up with
the JSF folks so we can decide how to resurrect those.<br>
<br>
Overall writing integration tests should now be much easier.<br>
<br>
cheers<br>
-thomas<br>
</tt>- <br>
<pre class="moz-signature" cols="72">xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
</pre>
</body>
</html>