<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Jason,<br>
<blockquote
cite="mid:BANLkTindh_6D0FO3R4cebDpJoNgpj=qXyg@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">1.
I think I will need a test suite with the test classes in<br>
src/main/java (rather than src/test/java) so that the provider can get<br>
those classes onto its own classpath during testing. Will Arquillian<br>
work OK like that (ie: does it have maven integration which specifically<br>
looks under src/test/java only)?<br>
</blockquote>
<div><br>
</div>
<div>No, there's nothing in there that I'm aware of that would
prohibit this approach.</div>
</div>
</blockquote>
You're right of course. The thing that seems to be getting in my way is
actually the Surefire Maven plugin. I've created the TCK project
separately and configured the Compile plugin to generate a
seam-cron-asynchronous-tck-tests.jar which I'm then including in the
asynchronous provider's project like so:<br>
<br>
<dependency><br>
<groupId>${project.groupId}</groupId><br>
<artifactId>seam-cron-asynchronous-tck</artifactId><br>
<version>${project.version}</version><br>
<type>test-jar</type><br>
<scope>test</scope><br>
</dependency><br>
<br>
However Maven still concludes that there aren't any test to run for
that project. I suppose that's for good reason, but I'd like to work
out how I can have these imported tests run by Surefire, rather than
just the ones in src/test/java. I'll keep trying but please chime in if
anyone has any ideas.<br>
<blockquote
cite="mid:BANLkTindh_6D0FO3R4cebDpJoNgpj=qXyg@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2.
The classes in the test suite have a hard-coded @Deployment, and I'm<br>
not sure how I'd go about customising that place a different provider<br>
class on the classpath. I don't want to have to force my providers to<br>
extend every test case just to customise the deployment.<br>
</blockquote>
<div><br>
</div>
<div>You're @Deployment should be in the test class, but that doesn't
stop you from having a base method that setup everything and just
returns an archive you can add to, or even merge(...) in your
@Deployement method.</div>
</div>
</blockquote>
Would this require me to extend each of the TCK test classes in the
provider project, in order to be able to add to the archive returned by
the base method? This is something I wanted to avoid (even though it
would clearly solve problem 1).<br>
<br>
Cheers,<br>
<br>
Pete R<br>
</body>
</html>