July 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-892) Should be able to reference the real disk resources in rebel.xml where applicable

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-892: --------------------------------- Summary: Should be able to reference the real disk resources in rebel.xml where applicable Key: ARQ-892 URL: https://issues.jboss.org/browse/ARQ-892 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - JRebel Reporter: Aslak Knutsen Assignee: Bernard Labno Fix For: jrebel_1.0.0.next General notes: https://gist.github.com/2483202 -- 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, 11 months

2
7
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, 11 months

1
2
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, 11 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, 11 months

1
4
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, 11 months

2
6
0 / 0

[JBoss JIRA] (ARQ-929) Drone: Switch useJavaScript to true by default

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-929: ------------------------------ Summary: Drone: Switch useJavaScript to true by default Key: ARQ-929 URL: https://issues.jboss.org/browse/ARQ-929 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Lukáš Fryč Assignee: Karel Piwko No one uses {{htmlUnit}} without {{useJavaScript=true}}. Document properly. -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] (ARQ-1008) Can't use reusable remote driver with opera - NotSerializableException

by Jan Papousek (JIRA)

Jan Papousek created ARQ-1008: --------------------------------- Summary: Can't use reusable remote driver with opera - NotSerializableException Key: ARQ-1008 URL: https://issues.jboss.org/browse/ARQ-1008 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone 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, 11 months

2
12
0 / 0

[JBoss JIRA] Created: (ARQ-563) @ArquillianResource in TestNG based tests causes test body not to be evaluated

by Karel Piwko (JIRA)

@ArquillianResource in TestNG based tests causes test body not to be evaluated ------------------------------------------------------------------------------ Key: ARQ-563 URL: https://issues.jboss.org/browse/ARQ-563 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Protocol SPIs and Implementation Affects Versions: 1.0.0.CR4 Environment: Surefire 2.7.2, 2.9 TestNG 5.14.6, 5.14.9 AS 7.0.1 web Reporter: Karel Piwko Priority: Blocker Suppose following test case: {code} public class LowercaseConverterTest extends Arquillian { @Inject private LowercaseConverter lowercaseConverter; @Deployment public static JavaArchive createTestArchive() { return ShrinkWrap .create(JavaArchive.class, "test.jar") .addClasses(LowercaseConverter.class) .addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); } @Test public void testConvertToLowercase() { Assert.assertEquals("martin", lowercaseConverter.convertToLowercase("Martin")); } } {code} However, if @ArquillianResource is used for a field injection, such as: {code} @ArquillianResource URL field; {code} than test body is no longer executed and *all tests are reported as passed* even an obvious failure like: {code} @Test public void testConvertToLowercase() { Assert.fail(); Assert.assertEquals("karel", lowercaseConverter.convertToLowercase("Martin")); } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

10
17
0 / 0

[JBoss JIRA] (ARQ-961) Error in README for the name of additional URL qualifier

by Ken Finnigan (JIRA)

Ken Finnigan created ARQ-961: -------------------------------- Summary: Error in README for the name of additional URL qualifier Key: ARQ-961 URL: https://issues.jboss.org/browse/ARQ-961 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Portal Affects Versions: portal_1.0.0.Alpha1 Reporter: Ken Finnigan Assignee: Ken Finnigan Fix For: portal_1.0.0.next Qualifier on URL for tests is @PortalURL and not @PortalResource -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] (ARQ-817) arquillian-weld-container does not build on Maven Default Profile

by Andrew Rubinger (JIRA)

Andrew Rubinger created ARQ-817: ----------------------------------- Summary: arquillian-weld-container does not build on Maven Default Profile Key: ARQ-817 URL: https://issues.jboss.org/browse/ARQ-817 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Andrew Rubinger Assignee: Andrew Rubinger The current configuration assumes that the JBoss Nexus repo is enabled: {code}[ERROR] Failed to execute goal on project arquillian-weld-se-embedded-1.1: Could not resolve dependencies for project org.jboss.arquillian.container:arquillian-weld-se-embedded-1.1:jar:1.0.0.Final-SNAPSHOT: Could not find artifact org.jboss.weld:weld-core:jar:1.1.1.Final in central (http://repo.maven.apache.org/maven2) -> [Help 1]{code} Probably we could go for an upgrade of Weld here anyway, which has been proxied to Maven Central. -- 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, 11 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2012