September 2013 - arquillian-issues

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-591?page=com.atlassian.jira.plugin.sy... ] Karel Piwko closed ARQ-591. --------------------------- > 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 - QUnit > Reporter: Lukáš Fryč > Assignee: Tolis Emmanouilidis > Fix For: qunit_1.0.0.Alpha1 > > > 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. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-591?page=com.atlassian.jira.plugin.sy... ] Karel Piwko resolved ARQ-591. ----------------------------- Resolution: Done This issues was resolved by releasing QUnit extension 1.0.0.Alpha1. > 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 - QUnit > Reporter: Lukáš Fryč > Assignee: Tolis Emmanouilidis > Fix For: qunit_1.0.0.Alpha1 > > > 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. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

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

by Falko M. (JIRA)

[ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.sy... ] Falko M. edited comment on ARQ-286 at 9/27/13 9:14 AM: ------------------------------------------------------- PS: In my custom rule I try to retrieve the beans that need to be injected into the test instance but they are null at the time the rule runs (= injection has not been performed yet). It would be great if that could be addressed as well. It worked that way with Spring 3, btw. was (Author: famod): PS: In my custom rule I try to retrieve the injected beans but they are null at the time the rule runs (= injection has not been performed yet). It would be great if that could be addressed as well. It worked that way with Spring 3, btw. > 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 > Fix For: 2.0.0.CR1 > > > 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 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

12 years, 6 months

1
0
0 / 0

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

by Falko M. (JIRA)

[ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.sy... ] Falko M. commented on ARQ-286: ------------------------------ PS: In my custom rule I try to retrieve the injected beans but they are null at the time the rule runs (= injection has not been performed yet). It would be great if that could be addressed as well. It worked that way with Spring 3, btw. > 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 > Fix For: 2.0.0.CR1 > > > 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 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-383) Improve @Location for contextRoot

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-383?page=com.atlassian.jira.plugin... ] Juraj Húska commented on ARQGRA-383: ------------------------------------ Or we can provide default value for the {{@Location}}, thus user will be able to denote location value equals to the {{contextRoot}} like: {code} @Location public class MyPageObject { } {code} > Improve @Location for contextRoot > --------------------------------- > > Key: ARQGRA-383 > URL: https://issues.jboss.org/browse/ARQGRA-383 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Karel Piwko > Priority: Minor > > In cases when @Location represents @ArquillianResource URL contextPath, it might be confusing that user needs to set it to: > {code} > @Location("") > {code} > It might be more convenient to provide a better way how to say that location equals contextPath, maybe *@DeploymentLocation or something like that. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-383) Improve @Location for contextRoot

by Karel Piwko (JIRA)

Karel Piwko created ARQGRA-383: ---------------------------------- Summary: Improve @Location for contextRoot Key: ARQGRA-383 URL: https://issues.jboss.org/browse/ARQGRA-383 Project: Arquillian Graphene Issue Type: Enhancement Reporter: Karel Piwko Priority: Minor In cases when @Location represents @ArquillianResource URL contextPath, it might be confusing that user needs to set it to: {code} @Location("") {code} It might be more convenient to provide a better way how to say that location equals contextPath, maybe *@DeploymentLocation or something like that. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-382) @InitialPage does not work for Field

by Karel Piwko (JIRA)

Karel Piwko created ARQGRA-382: ---------------------------------- Summary: @InitialPage does not work for Field Key: ARQGRA-382 URL: https://issues.jboss.org/browse/ARQGRA-382 Project: Arquillian Graphene Issue Type: Bug Components: core Affects Versions: 2.0.0.CR1 Reporter: Karel Piwko While @InitialPage allows to be used on test class field, it does not do anything. {code} @InitialPage AddUserPage page; @Test void test() { page.foo() } {code} raises {code} java.lang.NullPointerException: null at com.acme.example.test.DroneTest.addUser(DroneTest.java:35) {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1496) Add a Tomcat 8 embedded container

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/ARQ-1496?page=com.atlassian.jira.plugin.s... ] Martin Kouba updated ARQ-1496: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-tomcat/pull/20 > Add a Tomcat 8 embedded container > --------------------------------- > > Key: ARQ-1496 > URL: https://issues.jboss.org/browse/ARQ-1496 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Martin Kouba > Assignee: Martin Kouba > > {{arquillian-tomcat-embedded-7}} is not compatible with Tomcat 8 due to {{org.apache.catalina.startup.HostConfig}} does not declare {{appBase()}} method anymore. It seems {{host.getAppBaseFile()}} should be used instead. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-381) Support for robust and concise way of asserting instances of WebDriver

by Juraj Húska (JIRA)

Juraj Húska created ARQGRA-381: ---------------------------------- Summary: Support for robust and concise way of asserting instances of WebDriver Key: ARQGRA-381 URL: https://issues.jboss.org/browse/ARQGRA-381 Project: Arquillian Graphene Issue Type: Enhancement Components: core Affects Versions: 2.0.0.CR1 Reporter: Juraj Húska In the old days, it was possible to figure out which browser the test is running on by: {code} GrapheneContext.holdsInstanceOf(AndroidDriver.class) {code} In the current Graphene this information can be retrieved IMHO in quite verbose way. E.g. [this|https://github.com/richfaces/richfaces/blob/master/build/build-resou...] piece of code to find out whether the browser is {{PhnatomJS}}. Can we provide some robust and concise shortcut for this ? -- 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

12 years, 6 months

1
0
0 / 0

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

by Falko M. (JIRA)

[ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.sy... ] Falko M. commented on ARQ-286: ------------------------------ I stumbled upon this issue when trying to look up something from JNDI within my custom junit rule. And then I saw it is executed twice... {quote} In the end the behavior for the @Rule annotation should be the same as for @Before/@After (execute the rule only on the container if we are in Client mode). {quote} I think so! > 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 > Fix For: 2.0.0.CR1 > > > 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 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

12 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2013