September 2015 - arquillian-issues

[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 commented on ARQ-286: ----------------------------------- Do you have the code/pom example somewhere? > 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 > Assignee: 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.4.11#64026)

8 years, 7 months

1
0
0 / 0

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

by Luca Stancapiano (JIRA)

[ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.sy... ] Luca Stancapiano commented on ARQ-286: -------------------------------------- I'm triing arquillian 1.1.7 with the same code in mode 'in container' so: {code:java} @RunWith(Arquillian.class) public class TestCase { @Rule public ExpectedException e = ExpectedException.none(); @Test public void test() { e.expect(RuntimeException.class) throw new RuntimeException(); } } {code} I see that the rule is executed anyhow in the client side. Should it run in the container side? > 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 > Assignee: 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.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-477) Upgrade to Core 1.1.8, Drone 2.0.0.Alpha5, Selenium 2.47.1

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-477: --------------------------------- Summary: Upgrade to Core 1.1.8, Drone 2.0.0.Alpha5, Selenium 2.47.1 Key: ARQGRA-477 URL: https://issues.jboss.org/browse/ARQGRA-477 Project: Arquillian Graphene Issue Type: Component Upgrade Reporter: Lukáš Fryč -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-476) Extend root element from GrapheneElement

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-476?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-476: --------------------------------- Assignee: Michael Kotten > Extend root element from GrapheneElement > ----------------------------------------- > > Key: ARQGRA-476 > URL: https://issues.jboss.org/browse/ARQGRA-476 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.3.Final, 2.1.0.Alpha2 > Reporter: Michael Kotten > Assignee: Michael Kotten > Priority: Minor > > Currently the root element in page fragments must extend WebElement. I would like to extend this, so it can also extend GrapheneElement. I'm preparing a pull request for this currently. Would be nice if this enhancement would make it to the next release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-475) Support inheritance for page fragments delegating to WebElement

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-475?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-475: --------------------------------- Assignee: Michael Kotten > Support inheritance for page fragments delegating to WebElement > --------------------------------------------------------------- > > Key: ARQGRA-475 > URL: https://issues.jboss.org/browse/ARQGRA-475 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.3.Final, 2.1.0.Alpha2 > Reporter: Michael Kotten > Assignee: Michael Kotten > Priority: Minor > > When implementing page fragments that extend WebElement as described in https://docs.jboss.org/author/display/ARQGRA2/Delegate+to+WebElement it is not possible to use superclasses for this construct. > This is because the method {{isAboutToDelegateToWebElement}} in {{PageFragmentEnricher}} just searches the current class, but not the superclasses. > I'm preparing a minor change for this currently. Hope to send the pull request soon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-475) Support inheritance for page fragments delegating to WebElement

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-475?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-475: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/133/files > Support inheritance for page fragments delegating to WebElement > --------------------------------------------------------------- > > Key: ARQGRA-475 > URL: https://issues.jboss.org/browse/ARQGRA-475 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.3.Final, 2.1.0.Alpha2 > Reporter: Michael Kotten > Priority: Minor > > When implementing page fragments that extend WebElement as described in https://docs.jboss.org/author/display/ARQGRA2/Delegate+to+WebElement it is not possible to use superclasses for this construct. > This is because the method {{isAboutToDelegateToWebElement}} in {{PageFragmentEnricher}} just searches the current class, but not the superclasses. > I'm preparing a minor change for this currently. Hope to send the pull request soon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1237) Warp: use PortProber to determine free ports for proxy

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1237?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1237: --------------------------------- Thanks [~chschulz], this is nice contribution! > Warp: use PortProber to determine free ports for proxy > ------------------------------------------------------ > > Key: ARQ-1237 > URL: https://issues.jboss.org/browse/ARQ-1237 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Christian Schulz > Priority: Minor > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Selenium 2 uses {{PortProber}} to check free ports to run Selenium Server on. > We can leverage that component too for Warp proxy and avoid conflicting ports. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1237) Warp: use PortProber to determine free ports for proxy

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1237?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned ARQ-1237: ------------------------------- Assignee: Christian Schulz (was: Bartosz Majsak) > Warp: use PortProber to determine free ports for proxy > ------------------------------------------------------ > > Key: ARQ-1237 > URL: https://issues.jboss.org/browse/ARQ-1237 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Christian Schulz > Priority: Minor > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Selenium 2 uses {{PortProber}} to check free ports to run Selenium Server on. > We can leverage that component too for Warp proxy and avoid conflicting ports. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1237) Warp: use PortProber to determine free ports for proxy

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1237?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1237: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Warp: use PortProber to determine free ports for proxy > ------------------------------------------------------ > > Key: ARQ-1237 > URL: https://issues.jboss.org/browse/ARQ-1237 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Christian Schulz > Priority: Minor > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Selenium 2 uses {{PortProber}} to check free ports to run Selenium Server on. > We can leverage that component too for Warp proxy and avoid conflicting ports. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1981) Warp: leverage Chameleon for broader container-coverage

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1981?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1981: ---------------------------- Description: Arquillian Chameleon allows for simple switching between various container implementations, modes and versions: http://arquillian.org/modules/arquillian-container-chameleon-container-ad... We could leverage Chameleon in order to test Warp against functionally against different containers, modes and versions. > Warp: leverage Chameleon for broader container-coverage > ------------------------------------------------------- > > Key: ARQ-1981 > URL: https://issues.jboss.org/browse/ARQ-1981 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Reporter: Lukáš Fryč > > Arquillian Chameleon allows for simple switching between various container implementations, modes and versions: > http://arquillian.org/modules/arquillian-container-chameleon-container-ad... > We could leverage Chameleon in order to test Warp against functionally against different containers, modes and versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2015