[JBoss JIRA] (ARQ-1220) Make Remote Coverage data available to IDE
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-1220:
----------------------------------
Summary: Make Remote Coverage data available to IDE
Key: ARQ-1220
URL: https://issues.jboss.org/browse/ARQ-1220
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Jacoco
Affects Versions: jacoco_1.0.0.Alpha3
Reporter: Aslak Knutsen
Story:
*In order to* view the collected coverage data
*As a* Tester
*I want to* get the feedback in the channel I'm currently viewing
Scenario:
*Given* that I run the test suite with Maven
*When* the Jacoco Maven Report plugin is active
*Then* the Jacoco Extension should write out the collected data to disk
*Given* that I run the test suite in Eclipse IDE
*When* the ElcEmma Jacoco IDE Plugin is active
*Then* the Jacoco Extension should report the data to the plugin
Rationale:
The Jacoco Extension has no idea if it's running in Maven or IDE and will only dump the data to the configured output directory. This works fine for Maven as the communication between the Jacoco Runner and Jacoco Reporter is file based. But this does not seem to be the case when executed from IDE. The Jacoco Extension should detect where it's running from and provide both with the data in the way they want.
The collected remote coverage data should be viewable in IDE, merged with the locally collected coverage data, when calling "Coverage As -> Junit".
--
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, 1 month
[JBoss JIRA] (ARQ-1219) Only collect remote coverage data when running in coverage mode
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-1219:
----------------------------------
Summary: Only collect remote coverage data when running in coverage mode
Key: ARQ-1219
URL: https://issues.jboss.org/browse/ARQ-1219
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Jacoco
Affects Versions: jacoco_1.0.0.Alpha3
Reporter: Aslak Knutsen
Story:
*In order to* be more efficient
*As a* Tester
*I want to* only collect remote coverage data when collecting local coverage data
Scenario:
*Given* that I have the Jacoco Extension on client classpath
*When* the client JVM is running in Coverage Mode
*Then* the Jacoco Extension should instrument the Deplomyent classes to collect remote coverage
*Given* that I have the Jacoco Extension on classpath
*When* the client JVM is _not_ running in Coverage Mode
*Then* the Jacoco Extension should do nothing
Rationale:
The Jacoco Extension will start recording remote coverage data as long as it's on classpath. As long as there is no one around to process the coverage data, that being a Maven Report plugin or a Eclipse IDE plugin, the remote data is useless.
--
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, 1 month
[JBoss JIRA] (ARQ-814) Should support injection of EJBs (as CDI Beans) in Weld Embedded
by Theo Gülcher (JIRA)
[ https://issues.jboss.org/browse/ARQ-814?page=com.atlassian.jira.plugin.sy... ]
Theo Gülcher commented on ARQ-814:
----------------------------------
Is there anything decided yet on this issue? Will it be solved and yes, for what version? I see no activity for over 8 months!
> Should support injection of EJBs (as CDI Beans) in Weld Embedded
> ----------------------------------------------------------------
>
> Key: ARQ-814
> URL: https://issues.jboss.org/browse/ARQ-814
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Weld Containers
> Affects Versions: weld_1.0.0.CR3
> Reporter: Anthony O.
> Assignee: Marko Lukša
> Attachments: EJBTest.java
>
>
> As seen in [this post on the Arquillian forum|https://community.jboss.org/message/723563], we cannot test that simple class as an NPE is thrown from {{org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.MockEjBServices}} which seems to be a copy of Weld code as [Aslak Knutsen|https://community.jboss.org/people/aslak] said.
> {code}
> @RunWith(Arquillian.class)
> public class EJBTest {
> @Deployment
> public static JavaArchive createTestArchive() {
> return ShrinkWrap
> .create(JavaArchive.class, "test.jar")
> .addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml"));
> }
> @Stateless
> public static class SomeService {
> public String someMethod() {
> return "test";
> }
> }
> @Inject
> SomeService someService;
> @Test
> public void testStatelessCall() {
> Assert.assertEquals("test", someService.someMethod());
> }
> }
> {code}
--
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, 1 month
[JBoss JIRA] (ARQ-1223) Warp JSF: refactor PhaseLifecycleEvent to expose name of the event when debugging
by Lukáš Fryč (JIRA)
Lukáš Fryč created ARQ-1223:
-------------------------------
Summary: Warp JSF: refactor PhaseLifecycleEvent to expose name of the event when debugging
Key: ARQ-1223
URL: https://issues.jboss.org/browse/ARQ-1223
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha1
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
Fix For: warp_1.0.0.Alpha2
When debugging Warp execution on server, all JSF phase events are exposed as {{PhaseLifecycleEvent}} - in order to improve debuggability, those events should have each own class in order to expose a name in debug output.
--
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, 1 month