July 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1818) JUnit @Before/After phase is called after/before Arquillian's Before/After phase

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1818?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1818: ------------------------------- Fix Version/s: 1.1.6.Final > JUnit @Before/After phase is called after/before Arquillian's Before/After phase > -------------------------------------------------------------------------------- > > Key: ARQ-1818 > URL: https://issues.jboss.org/browse/ARQ-1818 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Harness Integration > Affects Versions: 1.1.5.Final > Reporter: Aslak Knutsen > Fix For: 1.1.6.Final > > > In < 1.1.5.Final JUnit's @Before and @After was called by Arquillian as part of Arquillian's Before and After phases. This changed by accident during the JUnit Rule support rewrite and @Before is now called after Arquillian's Before and @After phase is now called Before Arquillian's After. > This break down APIs like Deployer/ContainerController as non of the Suite/Class/Test Contexts are active at that point. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1818) JUnit @Before/After phase is called after/before Arquillian's Before/After phase

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1818?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1818: ------------------------------- Priority: Critical (was: Major) > JUnit @Before/After phase is called after/before Arquillian's Before/After phase > -------------------------------------------------------------------------------- > > Key: ARQ-1818 > URL: https://issues.jboss.org/browse/ARQ-1818 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Harness Integration > Affects Versions: 1.1.5.Final > Reporter: Aslak Knutsen > Priority: Critical > Fix For: 1.1.6.Final > > > In < 1.1.5.Final JUnit's @Before and @After was called by Arquillian as part of Arquillian's Before and After phases. This changed by accident during the JUnit Rule support rewrite and @Before is now called after Arquillian's Before and @After phase is now called Before Arquillian's After. > This break down APIs like Deployer/ContainerController as non of the Suite/Class/Test Contexts are active at that point. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1818) JUnit @Before/After phase is called after/before Arquillian's Before/After phase

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/ARQ-1818?page=com.atlassian.jira.plugin.s... ] SBS JIRA Integration updated ARQ-1818: -------------------------------------- Forum Reference: https://community.jboss.org/thread/242571, https://community.jboss.org/message/880399#880399 (was: https://community.jboss.org/thread/242571) > JUnit @Before/After phase is called after/before Arquillian's Before/After phase > -------------------------------------------------------------------------------- > > Key: ARQ-1818 > URL: https://issues.jboss.org/browse/ARQ-1818 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Harness Integration > Affects Versions: 1.1.5.Final > Reporter: Aslak Knutsen > > In < 1.1.5.Final JUnit's @Before and @After was called by Arquillian as part of Arquillian's Before and After phases. This changed by accident during the JUnit Rule support rewrite and @Before is now called after Arquillian's Before and @After phase is now called Before Arquillian's After. > This break down APIs like Deployer/ContainerController as non of the Suite/Class/Test Contexts are active at that point. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1818) JUnit @Before/After phase is called after/before Arquillian's Before/After phase

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1818?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1818: ------------------------------- Forum Reference: https://community.jboss.org/thread/242571 > JUnit @Before/After phase is called after/before Arquillian's Before/After phase > -------------------------------------------------------------------------------- > > Key: ARQ-1818 > URL: https://issues.jboss.org/browse/ARQ-1818 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Harness Integration > Affects Versions: 1.1.5.Final > Reporter: Aslak Knutsen > > In < 1.1.5.Final JUnit's @Before and @After was called by Arquillian as part of Arquillian's Before and After phases. This changed by accident during the JUnit Rule support rewrite and @Before is now called after Arquillian's Before and @After phase is now called Before Arquillian's After. > This break down APIs like Deployer/ContainerController as non of the Suite/Class/Test Contexts are active at that point. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1818) JUnit @Before/After phase is called after/before Arquillian's Before/After phase

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1818: ---------------------------------- Summary: JUnit @Before/After phase is called after/before Arquillian's Before/After phase Key: ARQ-1818 URL: https://issues.jboss.org/browse/ARQ-1818 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Harness Integration Affects Versions: 1.1.5.Final Reporter: Aslak Knutsen In < 1.1.5.Final JUnit's @Before and @After was called by Arquillian as part of Arquillian's Before and After phases. This changed by accident during the JUnit Rule support rewrite and @Before is now called after Arquillian's Before and @After phase is now called Before Arquillian's After. This break down APIs like Deployer/ContainerController as non of the Suite/Class/Test Contexts are active at that point. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1816) Arquillian core is eating up framework exceptions

by Peter Probst (JIRA)

[ https://issues.jboss.org/browse/ARQ-1816?page=com.atlassian.jira.plugin.s... ] Peter Probst resolved ARQ-1816. ------------------------------- Fix Version/s: 1.1.5.Final Resolution: Done Thanks Aslak for pinpointing. Version 1.1.5.Final fixes the problem. > Arquillian core is eating up framework exceptions > ------------------------------------------------- > > Key: ARQ-1816 > URL: https://issues.jboss.org/browse/ARQ-1816 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Environment: wildfly 8.1.0.Final, arq bom 1.1.4.Final, persistence extension 1.0.0.Alpha7, shrinkwrap resolver bom 2.1.1 (and arquillian-suite-extension 1.1.1) > Reporter: Peter Probst > Fix For: 1.1.5.Final > > > using arquillian-suite-extension with arquillian-persistence-extension i found that arquillian is eating up severe exceptions. The test runner reports success on all tests - but non of the tests are running correctly. I have created a maven example project for arquillian-suite-extension to show the problem, that the suite extension is not working correctly with the persistence extension. This sample project can be used to reproduce also the exception handling problem. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1816) Arquillian core is eating up framework exceptions

by Peter Probst (JIRA)

[ https://issues.jboss.org/browse/ARQ-1816?page=com.atlassian.jira.plugin.s... ] Peter Probst commented on ARQ-1816: ----------------------------------- Hi Aslak, i will check... > Arquillian core is eating up framework exceptions > ------------------------------------------------- > > Key: ARQ-1816 > URL: https://issues.jboss.org/browse/ARQ-1816 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Environment: wildfly 8.1.0.Final, arq bom 1.1.4.Final, persistence extension 1.0.0.Alpha7, shrinkwrap resolver bom 2.1.1 (and arquillian-suite-extension 1.1.1) > Reporter: Peter Probst > > using arquillian-suite-extension with arquillian-persistence-extension i found that arquillian is eating up severe exceptions. The test runner reports success on all tests - but non of the tests are running correctly. I have created a maven example project for arquillian-suite-extension to show the problem, that the suite extension is not working correctly with the persistence extension. This sample project can be used to reproduce also the exception handling problem. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1816) Arquillian core is eating up framework exceptions

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1816?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1816: ------------------------------------ How about 1.1.5.Final? > Arquillian core is eating up framework exceptions > ------------------------------------------------- > > Key: ARQ-1816 > URL: https://issues.jboss.org/browse/ARQ-1816 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Environment: wildfly 8.1.0.Final, arq bom 1.1.4.Final, persistence extension 1.0.0.Alpha7, shrinkwrap resolver bom 2.1.1 (and arquillian-suite-extension 1.1.1) > Reporter: Peter Probst > > using arquillian-suite-extension with arquillian-persistence-extension i found that arquillian is eating up severe exceptions. The test runner reports success on all tests - but non of the tests are running correctly. I have created a maven example project for arquillian-suite-extension to show the problem, that the suite extension is not working correctly with the persistence extension. This sample project can be used to reproduce also the exception handling problem. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1817) Ad-hoc H2 java functions are treated as comments

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1817?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1817: -------------------------------- Fix Version/s: persistence_1.0.0.next > Ad-hoc H2 java functions are treated as comments > ------------------------------------------------ > > Key: ARQ-1817 > URL: https://issues.jboss.org/browse/ARQ-1817 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1817) Ad-hoc H2 java functions are treated as comments

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-1817: ----------------------------------- Summary: Ad-hoc H2 java functions are treated as comments Key: ARQ-1817 URL: https://issues.jboss.org/browse/ARQ-1817 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha7 Reporter: Bartosz Majsak Assignee: Bartosz Majsak -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2014