January 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1099) Add arquillian.xml configuration section to the documentation

by Martin Andersson (JIRA)

[ https://issues.jboss.org/browse/ARQ-1099?page=com.atlassian.jira.plugin.s... ] Martin Andersson commented on ARQ-1099: --------------------------------------- If you ask me, I can't understand why one would wanna write one single user guide or any other type of documentation before writing documentation about Arquillian.xml. We seriously need this file covered. > Add arquillian.xml configuration section to the documentation > -------------------------------------------------------------- > > Key: ARQ-1099 > URL: https://issues.jboss.org/browse/ARQ-1099 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Hardy Ferentschik > > At the moment there is no chapter in the documentation which describes the different workings of arquillian.xml. AFAIU each container adapter can have its own properties, but I think there is still a need to describe the basic workings, eg how to select a named container configuration via arquillian.launch. > See also: > * http://stackoverflow.com/questions/9740938/how-to-select-a-container-by-q... > * http://stackoverflow.com/questions/10119544/where-can-i-find-the-arquilli... > Given that arquillian.xml is the main configuration file it is only reasonable that people try to understand Arquillian from this angle. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-418) Upgrade to Selenium 2.39.0

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-418?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-418. ------------------------------- Resolution: Done > Upgrade to Selenium 2.39.0 > -------------------------- > > Key: ARQGRA-418 > URL: https://issues.jboss.org/browse/ARQGRA-418 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Components: integration > Affects Versions: 2.0.0.Final > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 2.0.1.Final > > -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-416) @InFrame duplicitly switches to iframe with fragment/page object method

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-416?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-416: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > @InFrame duplicitly switches to iframe with fragment/page object method > ----------------------------------------------------------------------- > > Key: ARQGRA-416 > URL: https://issues.jboss.org/browse/ARQGRA-416 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Assignee: Juraj Húska > Fix For: 2.0.1.Final > > > {code} > public class Fragment { > @FindBy(id="button") > private WebElement button; > public void clickButton() { > button.click(); > } > public WebElement getButton() { > return button; > } > } > {code} > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class Test { > //... > @FindBy(id="content") > @InFrame(nameOrId="frame") > private Fragment Fragment; > @Test > public void testWebElement() { > fragment.getButton().click(); //PASS > } > @Test > public void testMethod() { > fragment.clickButton(); //FAIL > } > } > {code} > Exception is: org.openqa.selenium.NoSuchFrameException: Unable to locate frame: frame -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-419) Upgrade to Drone 1.2.3.Final

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-419?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-419. ------------------------------- Resolution: Done > Upgrade to Drone 1.2.3.Final > ---------------------------- > > Key: ARQGRA-419 > URL: https://issues.jboss.org/browse/ARQGRA-419 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Components: integration > Affects Versions: 2.0.0.Final > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 2.0.1.Final > > -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-419) Upgrade to Drone 1.2.3.Final

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-419: --------------------------------- Summary: Upgrade to Drone 1.2.3.Final Key: ARQGRA-419 URL: https://issues.jboss.org/browse/ARQGRA-419 Project: Arquillian Graphene Issue Type: Component Upgrade Components: integration Affects Versions: 2.0.0.Final Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 2.0.1.Final -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-418) Upgrade to Selenium 2.39.0

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-418: --------------------------------- Summary: Upgrade to Selenium 2.39.0 Key: ARQGRA-418 URL: https://issues.jboss.org/browse/ARQGRA-418 Project: Arquillian Graphene Issue Type: Component Upgrade Components: integration Affects Versions: 2.0.0.Final Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 2.0.1.Final -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1633) Add osgi bundle on demand to managed karaf container

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-1633?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved ARQ-1633. --------------------------------- Resolution: Done Done in arquillian-container-karaf-managed-2.1.0.CR7 > Add osgi bundle on demand to managed karaf container > ---------------------------------------------------- > > Key: ARQ-1633 > URL: https://issues.jboss.org/browse/ARQ-1633 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: osgi_2.0.0.Final > > -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1633) Add osgi bundle on demand to managed karaf container

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-1633: ----------------------------------- Summary: Add osgi bundle on demand to managed karaf container Key: ARQ-1633 URL: https://issues.jboss.org/browse/ARQ-1633 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: osgi_2.0.0.Final -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1631) Deployment on isolated WLS managed servers

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/ARQ-1631?page=com.atlassian.jira.plugin.s... ] Vineet Reynolds updated ARQ-1631: --------------------------------- Component/s: WebLogic Containers > Deployment on isolated WLS managed servers > ------------------------------------------ > > Key: ARQ-1631 > URL: https://issues.jboss.org/browse/ARQ-1631 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebLogic Containers > Reporter: Vitalii Chepeliuk > > If WLS managed servers are clustered then to deploy any APP I need only specify target attr in arquillian.xml and one Deployment method > But if they are isolated and I need to deploy APP on each managed servers, like in following code > @Deployment(name = "wls_managed_8001") > @TargetsContainer("wsl01") > public static WebArchive createDeployment() { > WebArchive jar = createWebArchive(WAR_NAME) > .addAsManifestResource(MANIFEST_FILE_NAME); > return jar; > } > @Deployment(name = "wls_managed_8002") > @TargetsContainer("wls02") > public static WebArchive createDeployment2() { > WebArchive jar = createWebArchive(WAR_NAME) > .addAsManifestResource(MANIFEST_FILE_NAME); > return jar; > } > @Test > @InSequence(1) > @OperateOnDeployment("wls_managed_8001") > public void testAddData_wls01() throws Exception { > // Add some data to APP > } > @Test > @InSequence(2) > @OperateOnDeployment("wls_managed_8002") > public void testCheckData_wls02() throws Exception { > // Verify if data are propagated > } > But there is NO support for it cause every APP we want to deploy is managed through AdminServer and then it is sending it to managed servers -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1631) Deployment on isolated WLS managed servers

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/ARQ-1631?page=com.atlassian.jira.plugin.s... ] Vineet Reynolds updated ARQ-1631: --------------------------------- Affects Version/s: wls_1.0.0.Alpha2 > Deployment on isolated WLS managed servers > ------------------------------------------ > > Key: ARQ-1631 > URL: https://issues.jboss.org/browse/ARQ-1631 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebLogic Containers > Affects Versions: wls_1.0.0.Alpha2 > Reporter: Vitalii Chepeliuk > > If WLS managed servers are clustered then to deploy any APP I need only specify target attr in arquillian.xml and one Deployment method > But if they are isolated and I need to deploy APP on each managed servers, like in following code > @Deployment(name = "wls_managed_8001") > @TargetsContainer("wsl01") > public static WebArchive createDeployment() { > WebArchive jar = createWebArchive(WAR_NAME) > .addAsManifestResource(MANIFEST_FILE_NAME); > return jar; > } > @Deployment(name = "wls_managed_8002") > @TargetsContainer("wls02") > public static WebArchive createDeployment2() { > WebArchive jar = createWebArchive(WAR_NAME) > .addAsManifestResource(MANIFEST_FILE_NAME); > return jar; > } > @Test > @InSequence(1) > @OperateOnDeployment("wls_managed_8001") > public void testAddData_wls01() throws Exception { > // Add some data to APP > } > @Test > @InSequence(2) > @OperateOnDeployment("wls_managed_8002") > public void testCheckData_wls02() throws Exception { > // Verify if data are propagated > } > But there is NO support for it cause every APP we want to deploy is managed through AdminServer and then it is sending it to managed servers -- 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

10 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 2014