[JBoss JIRA] (ARQ-1309) Persistence extension does not work with Jacoco extension
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1309?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1309:
-------------------------------
Fix Version/s: persistence_1.0.0.Alpha7
(was: persistence_1.0.0.next)
> Persistence extension does not work with Jacoco extension
> ---------------------------------------------------------
>
> Key: ARQ-1309
> URL: https://issues.jboss.org/browse/ARQ-1309
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: 1.0.0.Alpha5
> Reporter: Peter Schonhofen
> Assignee: Bartosz Majsak
> Fix For: persistence_1.0.0.Alpha7
>
>
> When the Jacoco and persistence extension is used together in a project, a "PersistenceExtensionInitializationException: Unable to create persistence configuration" is thrown.
> The cause of the exception is that in the ConfigurationImporter class the createConfiguration method receives a fieldsWithValues map with a "$jacocoData" item in it. Because the method cannot process this item, it fails.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ARQ-1664) Provide custom table filter for seeding and cleaning databases
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1664?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1664:
-------------------------------
Fix Version/s: persistence_1.0.0.Alpha7
(was: persistence_1.0.0.next)
> Provide custom table filter for seeding and cleaning databases
> --------------------------------------------------------------
>
> Key: ARQ-1664
> URL: https://issues.jboss.org/browse/ARQ-1664
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha6
> Reporter: Bartosz Majsak
> Assignee: Bartosz Majsak
> Fix For: persistence_1.0.0.Alpha7
>
>
> In order to resolve Foreign Key dependency and remove tables in the correct order DatabaseSequenceFilter has been introduced. As it's causing significant performance drop, especially in Oracle DB, it should be possible to define custom table filtering through SPI mechanism. This is also useful when seeding database.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ARQ-1355) Access the DatabaseConnection for additional verifications in an arquillian test
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1355?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1355:
-------------------------------
Fix Version/s: persistence_1.0.0.Alpha7
(was: persistence_1.0.0.next)
> Access the DatabaseConnection for additional verifications in an arquillian test
> --------------------------------------------------------------------------------
>
> Key: ARQ-1355
> URL: https://issues.jboss.org/browse/ARQ-1355
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Reporter: Dominik Grupp
> Assignee: Bartosz Majsak
> Priority: Minor
> Fix For: persistence_1.0.0.Alpha7
>
>
> There should be a possibility in an arquillian test to access the DatabaseConnection for additional verifications using dbunit. Using @UsingDataSet and @ShouldMatchDataSet first the already provided verifications could be done but then additional verification with dbunit using the DatabaseConnection - e.g. verfiy with a rowcount to make sure not more entries than expected have been created by the test.
> Original post (with a code example): https://community.jboss.org/thread/222401?tstart=0
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ARQ-332) Add support for injectable configuration options
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-332?page=com.atlassian.jira.plugin.sy... ]
Aslak Knutsen updated ARQ-332:
------------------------------
Fix Version/s: 2.0.0.CR1
> Add support for injectable configuration options
> ------------------------------------------------
>
> Key: ARQ-332
> URL: https://issues.jboss.org/browse/ARQ-332
> Project: Arquillian
> Issue Type: Feature Request
> Components: Configuration
> Environment: All
> Reporter: John Ament
> Priority: Minor
> Fix For: 2.0.0.CR1
>
>
> I may have more of a unique situation here, not sure, but I figure something like this would be useful to a lot of people. In my case, I have to test my application against multiple RDBMSs. Amongst the test cases I need to execute, the only deltas between them is really the orm.xml and persistence.xml for JPA, since we override the configuration. Currently, arquillian requires me to point to the files in my test cases. Granted, I could use a static string to manage them, but I was wondering if arquillian could provide something like this in arquillian.xml
> <?xml version="1.0"?>
> <arquillian xmlns="http://jboss.com/arquillian"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:glassfish="urn:arq:org.jboss.arquillian.container.glassfish.embedded_3">
> <glassfish:container>
> <glassfish:sunResourcesXml>src/test/resources/sun-resources-mysql.xml</glassfish:sunResourcesXml>
> </glassfish:container>
> <properties>
> <property name="orm-xml" value="src/test/resources/orm-mysql.xml"/>
> <property name="persistence-xml" value="src/test/resources/pers-mysql.xml"/>
> </properties>
> </arquillian>
> And then in the test case itself
> @Inject ArquillianConfiguration config;
> config.getProperty("orm-xml");
> in order to access the property.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[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 commented on ARQ-1772:
------------------------------------
that would be this piece of code: https://github.com/arquillian/arquillian-core/blob/master/core/impl-base/...
It was added to avoid showing the 'anonymous innerclass' v of the ManagerStarted event.
> 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
>
> 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.3#6260)
10 years, 1 month
[JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-441?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-441:
------------------------------
Fix Version/s: 2.0.3.Final
> xhrInterception breaks applications using jQuery 2.x
> ----------------------------------------------------
>
> Key: ARQGRA-441
> URL: https://issues.jboss.org/browse/ARQGRA-441
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.0.0.Final, 2.0.2.Final
> Environment: Firefox 29, Chrome 34
> Reporter: Oliver Kišš
> Priority: Critical
> Fix For: 2.0.3.Final
>
>
> After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests.
> After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered).
> When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again.
> I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method
by Mattias Persson (JIRA)
[ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.s... ]
Mattias Persson updated ARQ-1773:
---------------------------------
Steps to Reproduce:
See attached file
Maven dependency according to:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.arquillian</groupId>
<artifactId>arquillian-bom</artifactId>
<version>1.1.4.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
Testclass according to:
package se.shouldfailtest;
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit.Arquillian;
import org.jboss.shrinkwrap.api.Archive;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.asset.EmptyAsset;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.Before;
import org.junit.Test;
import org.junit.runner.RunWith;
import static org.junit.Assert.assertTrue;
@RunWith(Arquillian.class)
public class ShouldFailTest {
@Deployment
public static Archive<?> createDeployment() {
WebArchive war = ShrinkWrap.create(WebArchive.class, "test.war")
.addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml");
return war;
}
@Before
public void preparePersistenceTest() throws Exception {
throw new Exception("Test should fail when exception is thrown in @Before...");
}
@Test
public void shouldFail() throws Exception {
//This test will pass in 1.1.4.Final but not in 1.1.3.Final (as expected).
assertTrue(false);
}
}
was:
See attached file.
Maven dependency according to:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.arquillian</groupId>
<artifactId>arquillian-bom</artifactId>
<version>1.1.4.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
Testclass according to:
package se.shouldfailtest;
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit.Arquillian;
import org.jboss.shrinkwrap.api.Archive;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.asset.EmptyAsset;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.Before;
import org.junit.Test;
import org.junit.runner.RunWith;
import static org.junit.Assert.assertTrue;
@RunWith(Arquillian.class)
public class ShouldFailTest {
@Deployment
public static Archive<?> createDeployment() {
WebArchive war = ShrinkWrap.create(WebArchive.class, "test.war")
.addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml");
return war;
}
@Before
public void preparePersistenceTest() throws Exception {
throw new Exception("Test should fail when exception is thrown in @Before...");
}
@Test
public void shouldFail() throws Exception {
//This test will pass in 1.1.4.Final but not in 1.1.3.Final (as expected).
assertTrue(false);
}
}
> JUnittests pass when exception is thrown from @Before-annotated method
> ----------------------------------------------------------------------
>
> Key: ARQ-1773
> URL: https://issues.jboss.org/browse/ARQ-1773
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Base Implementation
> Affects Versions: 1.1.4.Final
> Reporter: Mattias Persson
> Attachments: arquillian_test_should_fail.zip
>
>
> When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method
by Mattias Persson (JIRA)
[ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.s... ]
Mattias Persson updated ARQ-1773:
---------------------------------
Steps to Reproduce:
See attached file.
Maven dependency according to:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.arquillian</groupId>
<artifactId>arquillian-bom</artifactId>
<version>1.1.4.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
Testclass according to:
package se.shouldfailtest;
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit.Arquillian;
import org.jboss.shrinkwrap.api.Archive;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.asset.EmptyAsset;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.Before;
import org.junit.Test;
import org.junit.runner.RunWith;
import static org.junit.Assert.assertTrue;
@RunWith(Arquillian.class)
public class ShouldFailTest {
@Deployment
public static Archive<?> createDeployment() {
WebArchive war = ShrinkWrap.create(WebArchive.class, "test.war")
.addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml");
return war;
}
@Before
public void preparePersistenceTest() throws Exception {
throw new Exception("Test should fail when exception is thrown in @Before...");
}
@Test
public void shouldFail() throws Exception {
//This test will pass in 1.1.4.Final but not in 1.1.3.Final (as expected).
assertTrue(false);
}
}
was:
See attached file,
Maven dependency according to:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.arquillian</groupId>
<artifactId>arquillian-bom</artifactId>
<version>1.1.4.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
Testclass according to:
package se.shouldfailtest;
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit.Arquillian;
import org.jboss.shrinkwrap.api.Archive;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.asset.EmptyAsset;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.Before;
import org.junit.Test;
import org.junit.runner.RunWith;
import static org.junit.Assert.assertTrue;
@RunWith(Arquillian.class)
public class ShouldFailTest {
@Deployment
public static Archive<?> createDeployment() {
WebArchive war = ShrinkWrap.create(WebArchive.class, "test.war")
.addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml");
return war;
}
@Before
public void preparePersistenceTest() throws Exception {
throw new Exception("Test should fail when exception is thrown in @Before...");
}
@Test
public void shouldFail() throws Exception {
//This test will pass in 1.1.4.Final but not in 1.1.3.Final (as expected).
assertTrue(false);
}
}
> JUnittests pass when exception is thrown from @Before-annotated method
> ----------------------------------------------------------------------
>
> Key: ARQ-1773
> URL: https://issues.jboss.org/browse/ARQ-1773
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Base Implementation
> Affects Versions: 1.1.4.Final
> Reporter: Mattias Persson
> Attachments: arquillian_test_should_fail.zip
>
>
> When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month