snjeza/arquillian-eclipse

arquillian-eclipse's Issues

404 on Update site

Hi,
The update site "http://snjeza.github.com/arquillian-eclipse" for arquillian-eclipse tool is not working. Can you please let me know where can I get the update site for this tool.

Should default or ask for which Arquillian version to use

Steps

• new Workspace
• new Maven Project
• Configure -> Add Arquillian Support
  (Ignore the "Arquillian Settings" link in the dialog)
• Next

The generated POM now is invalid. It's missing <arquillian.version></arquillian.version>

The Arquillian Version settings should be included in the Setup dialog.

Missing parent Pom?

Importing this as a Maven project doesn't work. Only pom in core is found, and it's complaining bout missing parent pom?

Should not allow to "Create Arquillian Test Case" without having Arquillian setup

Recreate Steps

• Create a new maven project
• Right Click ->
  ** New Arquillian Test Case

At this point, you have a non compiling test.

The plugin should detect missing Arquillian Artifacts and ask to set it up first.

Allow Arquillian Validator to handle test cases without @Deployment method and no container

When running Arquillian tests in @RunAsClient mode, you don't need a @deployment method.

Client (e.g. Drone) can connect to a remote URL and act without a container completely.

I'm aware of more means (e.g. -standalone artifact) how to actually configure Arquillian to run without container/or without deployment.

Switch-button for enabling -Darquillian.debug=true for unit tests' and container's VM setup

-Darquillian.debug=true allow more insight into test lifecycle and drastically improves debugging experience by outputting call tree of Arquillian event system.

There is sample call tree for debugging Warp client-side full tree:

...
(E) Before
    (I) TestContextHandler.createSuiteContext
    (I) TestContextHandler.createClassContext
    (E) TestClass
    (I) TestContextHandler.createTestContext
    (I) ContainerEventController.createBeforeContext
    (O) DroneConfigurator.configureDrone
    (O) TestInstanceEnricher.enrich
    (E) BeforeEnrichment
    (E) RequireProxy
        (O) ProxyObserver.requireProxy
        (E) StartProxy
            (O) ProxyObserver.startProxy
    (E) AfterEnrichment
    (O) ClientBeforeAfterLifecycleEventExecuter.on
(E) Test
    (I) TestContextHandler.createSuiteContext
...

Similarly for container

---

The problem with debugging is that people need to setup VM arguments in Container Configuration

and then setup JUnit/TestNG VM arguments for each executed test specifically.

---

This button switch in toolbar should allow to add -Darquillian.debug=true to executed test (either JUnit or TestNG) and also into container configuration.

Should provide "Runtime Container" option if none are apecified

Steps

• new Maven project
• configure Arquillian
• create new Arquillian Test Case
• Run As Arquillian Test case

'Launching MyBeanTestCase has encountered and error. Arquillian tests require atleast one container on classpath"

If no profiles are active and/or none are defined as default, the plugin should suggest which profiles/containers to run this test with.