[JBoss JIRA] (ARQ-1319) Warp: Jacoco support
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1319?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on ARQ-1319:
---------------------------------
I guess the issue could be that server needs to be configured with agent setup.
> 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: 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
12 years, 8 months
[JBoss JIRA] (ARQ-1319) Warp: Jacoco support
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1319?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1319:
----------------------------
Attachment: warp-jacoco.png
> 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: 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
12 years, 8 months
[JBoss JIRA] (ARQ-1291) Warp: single request execution does enrich only first request
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1291?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1291:
----------------------------
Fix Version/s: warp_1.0.0.Beta1
(was: warp_1.0.0.Alpha3)
> Warp: single request execution does enrich only first request
> -------------------------------------------------------------
>
> Key: ARQ-1291
> URL: https://issues.jboss.org/browse/ARQ-1291
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Lukáš Fryč
> Priority: Blocker
> Fix For: warp_1.0.0.Beta1
>
>
> When single-request execution API is used
> {code}
> Warp.initiate(Activity)
> .inspect(Inspection);
> {code}
> then the default filter is applied which says that only first request can be enriched,
> and thus when user-provided filter selects second or further request, nothing will be enriched.
> In fact it should work in the way that first user-selected request is enriched.
--
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
12 years, 8 months
[JBoss JIRA] (ARQ-1319) Warp: Jacoco support
by Lukáš Fryč (JIRA)
Lukáš Fryč created ARQ-1319:
-------------------------------
Summary: 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
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
12 years, 8 months
[JBoss JIRA] (ARQ-1315) Make possible to configure firefox preferences via arquillian.xml
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1315?page=com.atlassian.jira.plugin.s... ]
Karel Piwko updated ARQ-1315:
-----------------------------
Affects Version/s: drone_1.2.0.Alpha2
> Make possible to configure firefox preferences via arquillian.xml
> -----------------------------------------------------------------
>
> Key: ARQ-1315
> URL: https://issues.jboss.org/browse/ARQ-1315
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_1.1.1.Final, drone_1.2.0.Alpha2
> Reporter: Fabian Schwarzer
> Assignee: Karel Piwko
>
> In order to configure a FF extension (see ARQ-1259) one needs to add properties to FF (like on the about:config page) via arquillian.xml. This could be done by preparing a FF profile and configure this in arquillian.xml. Unfortunately drone does not seem to pick up the firefox_profile property in arquillian.xml (propably due to org.openqa.selenium.firefox.FirefoxDriver.java:184)
> So it would be great if there were some means to configure FF properties; either by configuring them in the arquillian.xml like done in ARQ-1259, or by making it possible to pass a profile via
> <extension qualifier="webdriver">
> <property name="browserCapabilities">firefox</property>
> <property name="firefox_profile">/path/to/profile</property>
> </extension>
> see also ARQ-1245
--
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
12 years, 8 months