September 2013 - arquillian-issues

[JBoss JIRA] (ARQ-824) Verify Arquillian can run on JDK 1.5

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-824?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-824: ------------------------------ Fix Version/s: seam2_1.0.0.Beta1 > Verify Arquillian can run on JDK 1.5 > ------------------------------------ > > Key: ARQ-824 > URL: https://issues.jboss.org/browse/ARQ-824 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Seam2, JBoss AS Containers, Test Protocol SPIs and Implementation, Tomcat Containers > Affects Versions: 1.0.0.CR7 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: seam2_1.0.0.Beta1 > > > Setting compiler options target/source to 1.5 is not enough to verify that the code can actually run on JDK 1.5 since it ignores API changes. To avoid forcing developers to have JDK 1.5 installed to compile, we can add e.g. the Animal Sniffer Maven Plugin to verify using usage of JDK based on known api signatures. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1190) Identity not supported in Seam2 test enrichment injection

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1190?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1190: ------------------------------- Fix Version/s: seam2_1.0.0.Beta1 > Identity not supported in Seam2 test enrichment injection > --------------------------------------------------------- > > Key: ARQ-1190 > URL: https://issues.jboss.org/browse/ARQ-1190 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Seam2 > Affects Versions: seam2_1.0.0.Alpha2 > Reporter: Sean Tozer > Assignee: Bartosz Majsak > Fix For: seam2_1.0.0.Beta1 > > > Trying to @In inject the Identity component doesn't work, in that it just leaves it null. It doesn't, however, throw a required exception. Additionally, injecting another component which itself injects Identity does work. > It should be possible to inject Identity so that we can control which roles are active, which is important for testing user-specific behaviour. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1481) Remove redundancy of both ArquillianSputnik and ArquillianSpecification

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1481?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1481: ------------------------------------ <aslak> kpiwko why remove @ArquillianSpecification? ARQ-1481 <aslak> kpiwko i thought that was 'the spock' way and not RunWith? <aslak> (maybe that's only when you extend? ) <kpiwko> aslak: Sputnik does not have before/after suite events <kpiwko> so there is no way how to bind there but using the same way as Arquillian JUnit does <kpiwko> and for that, it is needed to have access to class constructor <kpiwko> so a different runner <kpiwko> I discussed that on spock ML <kpiwko> but Peter didn't want to create such hooks <kpiwko> or at least, not implemented this way...he was thking about aftershutdown hook <aslak> kpiwko hmm, but wouldn't you be able to do the same in the ASpockExtension as you do in ASputnik? <kpiwko> aslak: I don't think so...the AfterSuite hook is directly in run method <kpiwko> and spock does not give you access to RunNotiifer anywhare in annotated extension <aslak> kpiwko no, but it's only there because that's where we could hook in with junit. it basically runs After the last known test <aslak> similar you could use setupSpec/cleanupSpec <aslak> for each setupSpec +1 counter, for each cleanupSpec -1 counter. in cleanupSpec if counter == 0, fire AfterSuite <aslak> same with in setupSpec if counter == 0 fire BeforeSuite <kpiwko> that might work <aslak> in spock you should be able to get away from the ThreadLocal State stuff as well, since you only hvae one Instance of the interceptor and can control the creation of TestRunnerAdapter internally <kpiwko> aslak: that would be nice > Remove redundancy of both ArquillianSputnik and ArquillianSpecification > ----------------------------------------------------------------------- > > Key: ARQ-1481 > URL: https://issues.jboss.org/browse/ARQ-1481 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Beta1 > Reporter: Karel Piwko > Assignee: Karel Piwko > > It should be possible to remove @ArquillianSpecification, as it is redundant to @RunWith call. > {code} > @ArquillianSpecification > @RunWith(ArquillianSputik) > {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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1481) Remove redundancy of both ArquillianSputnik and ArquillianSpecification

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1481?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1481: -------------------------------- Assignee: Karel Piwko (was: Bartosz Majsak) > Remove redundancy of both ArquillianSputnik and ArquillianSpecification > ----------------------------------------------------------------------- > > Key: ARQ-1481 > URL: https://issues.jboss.org/browse/ARQ-1481 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Beta1 > Reporter: Karel Piwko > Assignee: Karel Piwko > > It should be possible to remove @ArquillianSpecification, as it is redundant to @RunWith call. > {code} > @ArquillianSpecification > @RunWith(ArquillianSputik) > {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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1445) Spock extension emits After/Before suite before/after each specification execution

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1445?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1445: ----------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-testrunner-spock/commit/32f05b32... Duplication of @RunWith and @ArquillianSpecification tracked in ARQ-1481. > Spock extension emits After/Before suite before/after each specification execution > ---------------------------------------------------------------------------------- > > Key: ARQ-1445 > URL: https://issues.jboss.org/browse/ARQ-1445 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Beta1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > Fix For: spock_1.0.0.next > > > Current Spock integration implementation is broken w.r.t. AfterSuite/BeforeSuite. > This leads to huge execution time and also breaks thinks that relies on being bootstrapped only once. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1480) After/Before methods are always fired on both container/in client

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1480?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1480: ----------------------------- Assignee: Aslak Knutsen (was: Bartosz Majsak) > After/Before methods are always fired on both container/in client > ----------------------------------------------------------------- > > Key: ARQ-1480 > URL: https://issues.jboss.org/browse/ARQ-1480 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Beta1 > Reporter: Karel Piwko > Assignee: Aslak Knutsen > Priority: Critical > Fix For: spock_1.0.0.next > > > Current behavior of setup() methods does not follow other Arquillian test runners. Namely, the problem is in method being always executed in both environments, making following call impossible: > {code} > @Inject Foo foo; > def setup() { > assert foo != null > } > {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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1480) After/Before methods are always fired on both container/in client

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1480?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1480: ----------------------------- Fix Version/s: spock_1.0.0.next > After/Before methods are always fired on both container/in client > ----------------------------------------------------------------- > > Key: ARQ-1480 > URL: https://issues.jboss.org/browse/ARQ-1480 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Beta1 > Reporter: Karel Piwko > Assignee: Bartosz Majsak > Priority: Critical > Fix For: spock_1.0.0.next > > > Current behavior of setup() methods does not follow other Arquillian test runners. Namely, the problem is in method being always executed in both environments, making following call impossible: > {code} > @Inject Foo foo; > def setup() { > assert foo != null > } > {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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1480) After/Before methods are always fired on both container/in client

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1480?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1480: ---------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-testrunner-spock/commit/59a36103.... Thanks Aslak! > After/Before methods are always fired on both container/in client > ----------------------------------------------------------------- > > Key: ARQ-1480 > URL: https://issues.jboss.org/browse/ARQ-1480 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Beta1 > Reporter: Karel Piwko > Assignee: Aslak Knutsen > Priority: Critical > Fix For: spock_1.0.0.next > > > Current behavior of setup() methods does not follow other Arquillian test runners. Namely, the problem is in method being always executed in both environments, making following call impossible: > {code} > @Inject Foo foo; > def setup() { > assert foo != null > } > {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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1481) Remove redundancy of both ArquillianSputnik and ArquillianSpecification

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1481: -------------------------------- Summary: Remove redundancy of both ArquillianSputnik and ArquillianSpecification Key: ARQ-1481 URL: https://issues.jboss.org/browse/ARQ-1481 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Spock TestRunner Affects Versions: spock_1.0.0.Beta1 Reporter: Karel Piwko Assignee: Bartosz Majsak It should be possible to remove @ArquillianSpecification, as it is redundant to @RunWith call. {code} @ArquillianSpecification @RunWith(ArquillianSputik) {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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1480) After/Before methods are always fired on both container/in client

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1480: -------------------------------- Summary: After/Before methods are always fired on both container/in client Key: ARQ-1480 URL: https://issues.jboss.org/browse/ARQ-1480 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Spock TestRunner Affects Versions: spock_1.0.0.Beta1 Reporter: Karel Piwko Assignee: Bartosz Majsak Priority: Critical Current behavior of setup() methods does not follow other Arquillian test runners. Namely, the problem is in method being always executed in both environments, making following call impossible: {code} @Inject Foo foo; def setup() { assert foo != null } {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

11 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2013