January 2015 - 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: ------------------------------- Affects 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 > Components: Test Harness Integration > Affects Versions: 1.1.5.Final, 1.1.6.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Priority: Blocker > Fix For: 1.1.7.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.3.11#6341)

9 years, 11 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: ------------------------------- Fix Version/s: 1.1.7.Final (was: 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 > Components: Test Harness Integration > Affects Versions: 1.1.5.Final, 1.1.6.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Priority: Blocker > Fix For: 1.1.7.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.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1904) ShrinkWrap Resolver upgrade 2.1.1

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1904: ---------------------------------- Summary: ShrinkWrap Resolver upgrade 2.1.1 Key: ARQ-1904 URL: https://issues.jboss.org/browse/ARQ-1904 Project: Arquillian Issue Type: Enhancement Components: Base Implementation Reporter: Aslak Knutsen Fix For: 1.1.6.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1904) ShrinkWrap Resolver upgrade 2.1.1

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1904?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen reassigned ARQ-1904: ---------------------------------- Assignee: Aslak Knutsen > ShrinkWrap Resolver upgrade 2.1.1 > --------------------------------- > > Key: ARQ-1904 > URL: https://issues.jboss.org/browse/ARQ-1904 > Project: Arquillian > Issue Type: Enhancement > Components: Base Implementation > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.6.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1905) ShrinkWrap Descriptors upgrade 2.0.0-alpha-6

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1905: ---------------------------------- Summary: ShrinkWrap Descriptors upgrade 2.0.0-alpha-6 Key: ARQ-1905 URL: https://issues.jboss.org/browse/ARQ-1905 Project: Arquillian Issue Type: Enhancement Components: Base Implementation Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.1.6.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1903) Support exploded deployments in WebLogic

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1903?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1903: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: wls_1.0.0.next Resolution: Done pushed upstream https://github.com/arquillian/arquillian-container-wls/commit/e0847b16028... > Support exploded deployments in WebLogic > ---------------------------------------- > > Key: ARQ-1903 > URL: https://issues.jboss.org/browse/ARQ-1903 > Project: Arquillian > Issue Type: Feature Request > Components: WebLogic Containers > Affects Versions: wls_1.0.0.Alpha3 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: wls_1.0.0.next > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1903) Support exploded deployments in WebLogic

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1903?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1903: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-wls/pull/16 > Support exploded deployments in WebLogic > ---------------------------------------- > > Key: ARQ-1903 > URL: https://issues.jboss.org/browse/ARQ-1903 > Project: Arquillian > Issue Type: Feature Request > Components: WebLogic Containers > Affects Versions: wls_1.0.0.Alpha3 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1903) Support exploded deployments in WebLogic

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1903?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen reassigned ARQ-1903: ---------------------------------- Assignee: Aslak Knutsen (was: Vineet Reynolds) > Support exploded deployments in WebLogic > ---------------------------------------- > > Key: ARQ-1903 > URL: https://issues.jboss.org/browse/ARQ-1903 > Project: Arquillian > Issue Type: Feature Request > Components: WebLogic Containers > Affects Versions: wls_1.0.0.Alpha3 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1903) Support exploded deployments in WebLogic

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1903: ---------------------------------- Summary: Support exploded deployments in WebLogic Key: ARQ-1903 URL: https://issues.jboss.org/browse/ARQ-1903 Project: Arquillian Issue Type: Feature Request Components: WebLogic Containers Affects Versions: wls_1.0.0.Alpha3 Reporter: Aslak Knutsen Assignee: Vineet Reynolds -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1902) Provide SPI for conditional execution of test methods

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1902?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1902: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/f4fef41f8fe812af7376... > Provide SPI for conditional execution of test methods > ----------------------------------------------------- > > Key: ARQ-1902 > URL: https://issues.jboss.org/browse/ARQ-1902 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.5.Final > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: 1.1.6.Final > > > [~aslak] > Let me explain. > We want to do this: > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class TestCase > { > @Test > @Jira("ARQ-1") > public void test() { > // this test method will be executed > // because Aslak created EJB Jar archive (JIRA status = done) > } > @Test > @Jira("ARQ-xyz") > public void test() { > // this methods will NOT be executed (will be skipped) > // becase lets say that its status is "open / unresolved" > } > } > {code} > While looking into the code, it seems these classes are most important (1), (2). > So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped. > In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly. > Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider and whole JIRA api on class path in my custom extension. > (1) https://github.com/arquillian/arquillian-core/blob/master/container/test-... > (2) https://github.com/arquillian/arquillian-core/blob/master/container/test-... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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 January 2015