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

[Aris Tzoumas (JIRA)]

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

Aris Tzoumas commented on ARQ-1319:
-----------------------------------

It is possible to decouple response's writing and closing from {{WarpFilter}} {{doFilterWarp}} method, but this means that I should have to do the following changes:
* Make {{RequestContextHandler}} observe {{BeforeSuite}} & {{AfterSuite}} instead of {{BeforeRequest}} & {{AfterRequest}} events. This way requestContext will be active throughout Arquillian's event lifecycle.
* Add two observer methods on {{HttpRequestProcessor}}. The first one will observe {{BeforeSuite}} event (with precedence 100)and replace {{HttpServletResponse}} with a {{NonWritingResponse}}. The second one will observe {{AfterSuite}} event (with precedence -100) and will write and close the {{ServletOutputStream}}.

Do you think that this is a good approach?
                
> 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