June 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1728?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic commented on ARQ-1728: ---------------------------------------- [~lfryc] it should be sufficient just to read server log file in a separate thread which would mimic the behaviour of file tailing, everything which would be written to some kind of buffer while test execution in logically inside a test method would be related to that particular test method and fired from logging extension as a reporting event > Add possibility to report AS console output related to test methods > ------------------------------------------------------------------- > > Key: ARQ-1728 > URL: https://issues.jboss.org/browse/ARQ-1728 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > > There is not any possiblity to see what AS has written out to console with test methods. > Investigate a way how to match output from AS with particular test method during which that console output has occured. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1606) Support deploymentExportPath to export Exploded

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1606?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1606. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/20507a7d0fce3b52a014... > Support deploymentExportPath to export Exploded > ----------------------------------------------- > > Key: ARQ-1606 > URL: https://issues.jboss.org/browse/ARQ-1606 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.2.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Currently deploymentExportPath will export a Zipped file, but the reason for exporting it is to see the content. Allow to export as exploded. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1742) Exception thrown before BeforeSuite event are not reported to user.

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1742?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1742. -------------------------------- Assignee: Aslak Knutsen Resolution: Done It seemed to me the failure happened in Junit either it was during boot or during beforeSuite, either way.. But couldn't hurt to handle the boot exceptions in the same way as beforeSuite. pushed upstream, https://github.com/arquillian/arquillian-core/commit/e43f9e99639874ab4bbe... > Exception thrown before BeforeSuite event are not reported to user. > ------------------------------------------------------------------- > > Key: ARQ-1742 > URL: https://issues.jboss.org/browse/ARQ-1742 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > *When*: > My extensions observes ManagerStarted event and something gets wrong and an exception is thrown. > *Then*: > Arquillian (Or rather JUnit) silently ignores the exception, causing subsequent children runs to be ignored: > https://github.com/arquillian/arquillian-core/blob/master/junit/core/src/... > This behavior should be improved. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1772) Arquillian Debug does not print real event class

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1772?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1772. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/a4d24f23d98369e0b548... > Arquillian Debug does not print real event class > ------------------------------------------------ > > Key: ARQ-1772 > URL: https://issues.jboss.org/browse/ARQ-1772 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > When using inheritance to define events, Arquillian Debug prints out following: > {code} > (E) PrepareDrone > (O) EventRegisterObserver.register > (O) DroneConfigurator.prepareDrone > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) Before > (O) EventRegisterObserver.register > (O) DroneLifecycleManager.before > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > {code} > Which is not really super useful, as debug log can't show what actual events were fired. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1801) @Before not called with arquillian-junit-standalone

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1801?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen reassigned ARQ-1801: ---------------------------------- Assignee: Aslak Knutsen > @Before not called with arquillian-junit-standalone > --------------------------------------------------- > > Key: ARQ-1801 > URL: https://issues.jboss.org/browse/ARQ-1801 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > When using > {code} > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-standalone</artifactId> > <version>1.1.4.Final</version> > </dependency> > {code} > @BeforeClass and @Before are not called. > Using arquillian-junit-container they are. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1801) @Before not called with arquillian-junit-standalone

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1801?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1801. -------------------------------- Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/d55ac3ca902b1ba91e49... > @Before not called with arquillian-junit-standalone > --------------------------------------------------- > > Key: ARQ-1801 > URL: https://issues.jboss.org/browse/ARQ-1801 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > When using > {code} > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-standalone</artifactId> > <version>1.1.4.Final</version> > </dependency> > {code} > @BeforeClass and @Before are not called. > Using arquillian-junit-container they are. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-181) When using @Test expected exception, the internal state of the TestResult is unknown

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-181?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-181: ------------------------------ Fix Version/s: 1.1.5.Final > When using @Test expected exception, the internal state of the TestResult is unknown > ------------------------------------------------------------------------------------ > > Key: ARQ-181 > URL: https://issues.jboss.org/browse/ARQ-181 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > JUnit > @Test(expected=Exception.class) > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG and JUnit to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-286) Should support JUnit @Rules

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-286: ------------------------------ Fix Version/s: 1.1.5.Final (was: 2.0.0.CR1) > Should support JUnit @Rules > --------------------------- > > Key: ARQ-286 > URL: https://issues.jboss.org/browse/ARQ-286 > Project: Arquillian > Issue Type: Feature Request > Components: Test Harness Integration > Reporter: Aslak Knutsen > Fix For: 1.1.5.Final > > > Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. > It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1437) NPE in ExceptionProxy.readExternal() for root cause leads to deserializationProblem = true

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1437?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1437: ------------------------------- Fix Version/s: 1.1.5.Final > NPE in ExceptionProxy.readExternal() for root cause leads to deserializationProblem = true > ------------------------------------------------------------------------------------------ > > Key: ARQ-1437 > URL: https://issues.jboss.org/browse/ARQ-1437 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.2.Final, 1.1.0.Final > Reporter: Falko M. > Priority: Minor > Fix For: 1.1.5.Final > > > See line 199 (for 1.0.2.Final): > {code} > // reset the cause, so we can de-serialize them individual > SecurityActions.setFieldValue(Throwable.class, original, "cause", causeProxy.createException()); > {code} > For the root cause of an exception, {{causeProxy}} will always be {{null}} and so a {{NullPointerException}} is thrown. > As the code is wrapped in a try block with follwoing catch block: > {code} > catch (Throwable e) // ClassNotFoundExcpetion / NoClassDefFoundError > { > // ignore, could not load class on client side, move on and create a fake 'proxy' later > deserializationProblem = true; > } > {code} > the NPE is caught and is "expected" to be a {{ClassNotFoundExcpetion}} or {{NoClassDefFoundError}} which is clearly not the case. > *Possible fix:* > {{original.cause}} should only be overwritten when {{causeProxy}} is *not* null. > *More context information:* > I came across this problem while trying to find the reason for an unexpected {{ArquillianProxyException}}: > {code}org.jboss.arquillian.test.spi.ArquillianProxyException: javax.ejb.EJBException : javax.persistence.OptimisticLockException [Proxied because : Original exception not deserilizable, ClassNotFoundException]{code} > The root problem was not the NPE, but the {{ClassNotFoundException}} mislead me and so I debugged {{ExceptionProxy}}. > I my case there is an {{InvalidClassException}} because of an older hibernate version on the client side. > +So that is another problem of {{ExceptionProxy}} as it assumes that only {{ClassNotFoundExcpetion}} or {{NoClassDefFoundError}} can occur!+ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1443) @ArquillianResource ManagementClient doesn't work (AS 7)

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1443?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1443: ------------------------------------ Correct. :) > @ArquillianResource ManagementClient doesn't work (AS 7) > -------------------------------------------------------- > > Key: ARQ-1443 > URL: https://issues.jboss.org/browse/ARQ-1443 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JBoss AS Containers > Affects Versions: 1.0.4.Final > Reporter: Ondrej Zizka > > {code} > @RunWith( Arquillian.class ) > public class ExtActionsMigrationTest extends ExternalMigratorsTestEnv { > @ArquillianResource private ManagementClient mc; > @Test > public void testCliAction() throws Exception { > TestUtils.printTestBanner(); > doTest( "CliActionTest", null, DirPreparation.NOOP ); > {code} > Exception: > {code} > Caused by: java.lang.RuntimeException: Provider for type class org.jboss.as.arquillian.container.ManagementClient returned a null value: org.jboss.as.arquillian.container.ManagementClientProvider@72bd402d > at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.lookup(ArquillianResourceTestEnricher.java:115) > at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.enrich(ArquillianResourceTestEnricher.java:57) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > ... > {code} > I'm using: > {code} > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-container</artifactId> > <scope>test</scope> > </dependency> > <dependency> > <groupId>org.jboss.as</groupId> > <artifactId>jboss-as-arquillian-container-managed</artifactId> > <version>${arq.asContainer.version}</version> > <scope>test</scope> > <exclusions><exclusion> <artifactId>jbosgi-spi</artifactId> <groupId>org.jboss.osgi.spi</groupId></exclusion> </exclusions> > </dependency> > {code} > JBoss EAP comes from org.jboss.as:jboss-as-dist:${as.download.version}:zip > Whole container config is below. > {code} > <container qualifier="jboss" default="true"> > <configuration> > <property name="jbossHome">${basedir}/target/as-dist</property> >  > <property name="javaVmArguments">-Djboss.inst=${basedir}/target/jboss-as-7.1.1.Final</property> > <property name="serverConfig">${jboss.server.config.file.name:standalone.xml}</property> > <property name="allowConnectingToRunningServer">true</property> > <property name="managementAddress">${node0:127.0.0.1}</property> > <property name="managementPort">${as.managementPort:9999}</property> >  > <property name="waitForPorts">${as.debug.port:8787} ${as.managementPort:9999}</property> > <property name="waitForPortsTimeoutInSeconds">8</property> > </configuration> > </container> > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues June 2014