Right, in that context it's needed.
You'll need a Deployment to run "In Container", but you can run without a
Deployment and just work as a standalone client.
You can even run without any Container/Deployment support enabled at all, just as a common
abstraction layer between different test frameworks, but...
Let's assume the most common use case, which is having a Deployment, and leave it as
is for now.
-aslak-
----- Original Message -----
On 16.10.2012 17:39, Aslak Knutsen wrote:
Wooha, you've been busy since last i had a look! Nice!
One comment of the top of my head:
- Validation: a Deployment method is not required.
The following is from the Getting started tutorial (
http://arquillian.org/guides/getting_started/ ) :
Now, about that flair. An Arquillian test case must have three
things:
1. A @RunWith(Arquillian.class) annotation on the class
2. A public static method annotated with @Deployment that returns
a ShrinkWrap archive
3. At least one method annotated with @Test
Snjeza
-aslak-
----- Original Message -----
Hi,
Could you please review
https://github.com/snjeza/arquillian-eclipse
?
Your suggestions are welcome.
Thanks,
Snjeza