September 2012 - arquillian-issues

[JBoss JIRA] (ARQGRA-169) Support uninstallation for page extensions, especially for interfaces annotated by @JavaScript

by Jan Papousek (JIRA)

Jan Papousek created ARQGRA-169: ----------------------------------- Summary: Support uninstallation for page extensions, especially for interfaces annotated by @JavaScript Key: ARQGRA-169 URL: https://issues.jboss.org/browse/ARQGRA-169 Project: Arquillian Graphene Issue Type: Feature Request Affects Versions: 2.0.0.Alpha1 Reporter: Jan Papousek Assignee: Jan Papousek -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
2
0 / 0

[JBoss JIRA] (ARQ-1032) Drone: shortcut for starting Selenium Server

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-1032: ------------------------------- Summary: Drone: shortcut for starting Selenium Server Key: ARQ-1032 URL: https://issues.jboss.org/browse/ARQ-1032 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.1.0.CR1 Reporter: Lukáš Fryč Assignee: Karel Piwko When starting Drone test development, user needs to obtain appropriate version of {{selenium-server.jar}}, start it with {{java}} and provide all necessary properties like {{chrome.driver.binary}}. Required information is already available in {{pom.xml}} (selenium version) and {{arquillian.xml}} (driver properties). To allow quick bootstrap, Drone should provide method for user to ramp up to development quickly. Following integration can be considered: * JBDS * Forge - {{drone start}} * Maven - {{mvn arquillian:drone-start}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
2
0 / 0

[JBoss JIRA] (ARQGRA-162) Prototype ftests which use custom page samples and servlet container

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-162: --------------------------------- Summary: Prototype ftests which use custom page samples and servlet container Key: ARQGRA-162 URL: https://issues.jboss.org/browse/ARQGRA-162 Project: Arquillian Graphene Issue Type: Enhancement Components: ftest Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 2.0.0.Alpha2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
7
0 / 0

[JBoss JIRA] (ARQRUSH-39) Enhance Positive/Negative buttons

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQRUSH-39: --------------------------------- Summary: Enhance Positive/Negative buttons Key: ARQRUSH-39 URL: https://issues.jboss.org/browse/ARQRUSH-39 Project: Arquillian RushEye Issue Type: Enhancement Components: Manager Reporter: Lukáš Fryč Assignee: Jakub Dunia The possitive button should be called "Accept changes". Negative button can be removed, since its functionality would be duplicated with Next Case / Next Test. ---- "Accept changes" will actually act on what is selected: 1. if Test is selected * one particular test's pattern is accepted as new pattern, replacing the old one 2. if Case is selected * all the changes in underlying Case are accepted (adopted to current suite) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
5
0 / 0

[JBoss JIRA] (ARQRUSH-27) Implement change in structure: suite -> case* -> test* -> patterns+

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQRUSH-27: --------------------------------- Summary: Implement change in structure: suite -> case* -> test* -> patterns+ Key: ARQRUSH-27 URL: https://issues.jboss.org/browse/ARQRUSH-27 Project: Arquillian RushEye Issue Type: Task Components: Core, Manager Reporter: Lukáš Fryč Assignee: Lukáš Fryč To reflect test suites, Core should contain concept of {{case}} as container for tests. {{test}} then forms a base for one comparison. The new structure reflects how real functional tests maps to its output * one functional test method = one case * one functional test transition (image change) = one test See ARQRUSH-26 Support detection of changes in cases and tests (removals, additions, modifications) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (ARQ-591) Create extension for running JavaScript unit tests by Drone

by Lukáš Fryč (JIRA)

Create extension for running JavaScript unit tests by Drone ----------------------------------------------------------- Key: ARQ-591 URL: https://issues.jboss.org/browse/ARQ-591 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Lukáš Fryč This extension can handle several JS unit testing libraries, but at initial point, I suggest to go with QUnit [1]. At first, extension needs to go through available test definitions and prepare list of tests to provide it to test runner (JUnit/TestNG). At second, test needs to open tested page by Selenium (Drone). It would be necessary to run tests by several particular browser brands (HtmlUnit, Firefox, IE, ...). QUnit tests are traditionally at once - you open the page and all tests are ran. Then runner needs to collect all the results OR it can force QUnit to run only one test at time. [1] http://docs.jquery.com/Qunit -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
4
0 / 0

[JBoss JIRA] (ARQ-1110) can't create IPhoneDriver

by Jan Papousek (JIRA)

Jan Papousek created ARQ-1110: --------------------------------- Summary: can't create IPhoneDriver Key: ARQ-1110 URL: https://issues.jboss.org/browse/ARQ-1110 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: 1.0.2.Final Reporter: Jan Papousek Assignee: Jan Papousek IPhoneDriverFactory tries to create an IPhoneDriver with the given remote address and capabilities, but IPhoneDriver doesn't this type of constructor. {code} java.lang.IllegalStateException: Unable to find a constructor for implementation class org.openqa.selenium.iphone.IPhoneDriver(URL,DesiredCapabilities). Please make sure that you haven't misconfigured Arquillian Drone, e.g. you set an implementationClass which does not match the field/parameter type in your code. at org.jboss.arquillian.drone.webdriver.factory.SecurityActions.newInstance(SecurityActions.java:144) at org.jboss.arquillian.drone.webdriver.factory.IPhoneDriverFactory.createInstance(IPhoneDriverFactory.java:84) at org.jboss.arquillian.graphene.drone.factory.GrapheneIPhoneDriverFactory.createInstance(GrapheneIPhoneDriverFactory.java:74) at org.jboss.arquillian.graphene.drone.factory.GrapheneIPhoneDriverFactory.createInstance(GrapheneIPhoneDriverFactory.java:39) at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:129) at org.jboss.arquillian.graphene.drone.factory.GrapheneWebDriverFactory.createInstance(GrapheneWebDriverFactory.java:80) at org.jboss.arquillian.graphene.drone.factory.GrapheneWebDriverFactory.createInstance(GrapheneWebDriverFactory.java:41) at org.jboss.arquillian.drone.impl.DroneCreator.createWebTestBrowser(DroneCreator.java:71) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.drone.impl.DroneConfigurator.configureDrone(DroneConfigurator.java:116) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) at org.jboss.arquillian.testng.Arquillian.arquillianBeforeClass(Arquillian.java:103) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:77) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:110) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:106) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:113) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) {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, 8 months

3
6
0 / 0

[JBoss JIRA] (ARQ-1048) RemoteWebDriver ignores old configuration properties

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1048: -------------------------------- Summary: RemoteWebDriver ignores old configuration properties Key: ARQ-1048 URL: https://issues.jboss.org/browse/ARQ-1048 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.1.0.CR2 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: drone_1.2.0.next If you set up a Drone Webdriver with given capability, original configuration is completely ignored, e.g.: {code:java} public void simpleWebdriverTest(@Drone RemoteWebDriver webdriver) { webdriver.get(contextPath.toString()); webdriver.findElement(By.id("name")).sendKeys("Samuel"); webdriver.findElement(By.id("email")).sendKeys("samuel(a)vimes.dw"); webdriver.findElement(By.id("phoneNumber")).sendKeys("1234567890"); webdriver.findElement(By.id("register")).submit(); // FIXME with Graphene, you can wait for a request Assert.assertTrue(true); } {code} {code:xml}  <extension qualifier="webdriver"> <property name="browserCapabilities">${browser:chrome}</property> <property name="firefoxBinary">/opt/firefox-9.0.1/firefox-bin</property> <property name="chromeBinary">/opt/google/chrome/chrome</property> <property name="chromeSwitches">--user-data-dir=/tmp --disable-web-security</property> </extension> {code:xml} Both chromeBinary and chromeSwitches are ignored. If you use @Drone ChromeDriver instead, you get proper capabilities setup. This means that a mapping between capabilities and Arquillian properties has to be improved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
6
0 / 0

[JBoss JIRA] (ARQ-1113) Add @Deprecation to ConfigurationMapper.fromSystemConfiguration

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1113: -------------------------------- Summary: Add @Deprecation to ConfigurationMapper.fromSystemConfiguration Key: ARQ-1113 URL: https://issues.jboss.org/browse/ARQ-1113 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.1.0.CR3 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: drone_1.1.0.Final This method will be removed in 2.0.0 time 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

11 years, 8 months

2
2
0 / 0

[JBoss JIRA] (ARQ-1112) Verify Arquillian Drone can run on JDF 1.5

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1112: -------------------------------- Summary: Verify Arquillian Drone can run on JDF 1.5 Key: ARQ-1112 URL: https://issues.jboss.org/browse/ARQ-1112 Project: Arquillian Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Assignee: Karel Piwko Fix For: drone_1.1.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

11 years, 8 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2012