[arquillian-issues] [JBoss JIRA] (ARQ-1319) Warp: Jacoco support

Lukáš Fryč (JIRA) jira-events at lists.jboss.org
Mon Mar 4 04:12:57 EST 2013


    [ https://issues.jboss.org/browse/ARQ-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758078#comment-12758078 ] 

Lukáš Fryč edited comment on ARQ-1319 at 3/4/13 4:12 AM:
---------------------------------------------------------

I would consider it good approach, however the thing is that Warp currently misuses the Arquillian Manager - it should reuse it through whole test lifecycle and fire AfterSuite on the end of the test (ARQ-934).

Also, I have idea to avoid wrapping response (NonWritingResponse) at all: ARQ-1325

But as it appears to me, the CommandEventBus (and client test itself) should not finish before it has chance to process all Commands from server - it should wait from all server processing and all AfterSuite.

The ARQ-1325 and this issue could actually share implementation - the idea is allow bi-directional Command execution: test can execute command on server (e.g. "register the inspection", "execute AfterSuite"), on the other hand command service still can communicate to the client - I have this idea for quite long time: ARQ-1005
                
      was (Author: lfryc):
    I would consider it good approach, however the thing is that Warp currently misuses the Arquillian Manager - it should reuse it through whole test lifecycle and fire AfterSuite on the end of the test (ARQ-934).

Also, I have idea to avoid wrapping response (NonWritingResponse) at all: ARQ-1325

But as it appears to me, the CommandEventBus (and client test itself) should not finish before it has chance to process all Commands from server - it should wait from all server processing and all AfterSuite.

The ARQ-1325 and this issue could actually share implementation - the idea is allow bi-directional Command execution: test can execute command on server (e.g. "register the inspection", "execute AfterSuite"), on the other hand command service still can communicate to the client.
                  
> Warp: Jacoco support
> --------------------
>
>                 Key: ARQ-1319
>                 URL: https://issues.jboss.org/browse/ARQ-1319
>             Project: Arquillian
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Warp
>            Reporter: Lukáš Fryč
>             Fix For: warp_1.0.0.Beta1
>
>         Attachments: ftest-coverage.jpg, jacoco.jpg, warp-jacoco.png
>
>
> The support for CommandService was committed in ARQ-1027, which enabled us to run {{arquillian-extension-jacoco}}.
> However as report from the Warp's build shows, the reporting isn't successful - report doesn't seem to contain any hits.
> We need to investigate and once ready, we should use [{{check}}|http://www.eclemma.org/jacoco/trunk/doc/check-mojo.html] goal to be sure that coverage is reported successfully from Warp's tests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the arquillian-issues mailing list