[JBoss JIRA] (ARQGRA-230) Override a toString method in BooleanConditionWrapper
by Jiří Štefek (JIRA)
Jiří Štefek created ARQGRA-230:
----------------------------------
Summary: Override a toString method in BooleanConditionWrapper
Key: ARQGRA-230
URL: https://issues.jboss.org/browse/ARQGRA-230
Project: Arquillian Graphene
Issue Type: Enhancement
Reporter: Jiří Štefek
Priority: Trivial
It would be great if BooleanConditionWrapper had its own toString() method, so the logs from selenium could be more readable than:
{code}org.openqa.selenium.TimeoutException: Timed out after 5 seconds waiting for org.jboss.arquillian.graphene.condition.BooleanConditionWrapper@198de25e{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
[JBoss JIRA] (ARQ-1172) Implement an embedded WebLogic Server container
by Vineet Reynolds (JIRA)
Vineet Reynolds created ARQ-1172:
------------------------------------
Summary: Implement an embedded WebLogic Server container
Key: ARQ-1172
URL: https://issues.jboss.org/browse/ARQ-1172
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: WebLogic Containers
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Priority: Minor
WebLogic Server 12c supports EJB 3.1 and is hence expected to support testing of EJBs in an embedded container, at a minimum.
This feature request is to investigate implementation of the embedded Arquillian container for WLS 12c in particular. Support for an embedded mode of operation for WLS 10.3.x is to be investigated, and may be implemented if supported by Oracle (as documentated APIs or similar).
--
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
[JBoss JIRA] (ARQ-856) Embedded GlassFish adapter may use an incorrect HTTP port when a custom domain configuration XML file is used
by Vineet Reynolds (JIRA)
Vineet Reynolds created ARQ-856:
-----------------------------------
Summary: Embedded GlassFish adapter may use an incorrect HTTP port when a custom domain configuration XML file is used
Key: ARQ-856
URL: https://issues.jboss.org/browse/ARQ-856
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Vineet Reynolds
The embedded GlassFish container uses the default HTTP bind port of 8181, even though the user-supplied domain configuration XML file may specify a different HTTP port. This results in the following exception being thrown when the Arquillian client attempts to execute a test:
{code}
...
INFO: WELD-000900 SNAPSHOT
9 Apr, 2012 11:06:12 AM com.sun.enterprise.web.WebApplication start
INFO: WEB0671: Loading application [test] at [/test]
9 Apr, 2012 11:06:13 AM org.glassfish.deployment.admin.DeployCommand execute
INFO: test was successfully deployed in 18,014 milliseconds.
java.net.SocketException: Unexpected end of file from server
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:769)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:766)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1195)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.execute(ServletMethodExecutor.java:206)
at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.access$000(ServletMethodExecutor.java:43)
at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor$1.run(ServletMethodExecutor.java:99)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{code}
Note that the deployment is successful, but the {{HTTPContext}} returned by the embedded GlassFish adapter contains the wrong port information. In this case, the http-listener-1/http-listener-2 combo was registered in domain.xml to listen on 8080/8181. When Arquillian established a connection to port 8181, the container obviously did not respond to plain text HTTP traffic, and quite obviously the client errored out.
--
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
12 years
[JBoss JIRA] (ARQ-1208) Multiple line statements are not handled properly
by Bartosz Majsak (JIRA)
Bartosz Majsak created ARQ-1208:
-----------------------------------
Summary: Multiple line statements are not handled properly
Key: ARQ-1208
URL: https://issues.jboss.org/browse/ARQ-1208
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha5
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
When sql statement spans multiple lines it's not handled properly by the current implementation.
--
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
[JBoss JIRA] (ARQ-1204) Builder for Warp filters.
by Jakub Narloch (JIRA)
Jakub Narloch created ARQ-1204:
----------------------------------
Summary: Builder for Warp filters.
Key: ARQ-1204
URL: https://issues.jboss.org/browse/ARQ-1204
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha1
Reporter: Jakub Narloch
Assignee: Jakub Narloch
Fix For: warp_1.0.0.Alpha2
Warp could introduce some builder like functionality for creating filters in the test.
Example:
{code}
import static org.jboss.arquillian.warp.filter.HttpFilters.*;
HttpFilterBuilder restFilter = uri(contains("/rest/service"));
Warp.defaultFilter(restFilter);
Warp
.execute(...)
.filter(method(GET).uri(endsWith("/path1")))
.verify(...);
{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
[JBoss JIRA] (ARQ-1229) iOS extension Webdriver Build Error
by Lucas Holmquist (JIRA)
Lucas Holmquist created ARQ-1229:
------------------------------------
Summary: iOS extension Webdriver Build Error
Key: ARQ-1229
URL: https://issues.jboss.org/browse/ARQ-1229
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Extension - iOS
Reporter: Lucas Holmquist
There was a change in how the iOS webdriver version gets built in selenium
It no longer gets created in the Release-iphonesimulator directory, but instead the Debug-iphonesimulator
because of this, the ios extension will always build webdriver and fail to install it, since it is looking in the wrong place.
https://code.google.com/p/selenium/source/detail?r=18137
This is where it was changed in selenium and the reason they are keeping it
Simple fix PR incoming
--
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
[JBoss JIRA] (ARQGRA-228) Element condition matchers based on Strings
by Lukáš Fryč (JIRA)
Lukáš Fryč created ARQGRA-228:
---------------------------------
Summary: Element condition matchers based on Strings
Key: ARQGRA-228
URL: https://issues.jboss.org/browse/ARQGRA-228
Project: Arquillian Graphene
Issue Type: Enhancement
Reporter: Lukáš Fryč
Assignee: Jan Papousek
Currently, we may write this code:
{code:java}
waitGui().until(element(autocompleteInput).textEquals("A"));
{code}
If we want to add condition for waiting for input's value, we would add {{valueEquals}} method:
{code:java}
waitGui().until(element(autocompleteInput).valueEquals("A"));
{code}
But certainly, it would be best to use kind of value retrievers and their matchers with following API:
{code:java}
waitGui().until(element(autocompleteInput).text().equalTo("A"));
waitGui().until(element(autocompleteInput).value().equalTo("A"));
waitGui().until(element(autocompleteInput).value().contains("A"));
waitGui().until(attribute(autocompleteInput, "color").equalTo("A"));
{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
[JBoss JIRA] (ARQ-1071) NullPointerException when timeout is set in @Test when using JUnit
by Rick-Rainer Ludwig (JIRA)
Rick-Rainer Ludwig created ARQ-1071:
---------------------------------------
Summary: NullPointerException when timeout is set in @Test when using JUnit
Key: ARQ-1071
URL: https://issues.jboss.org/browse/ARQ-1071
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.1.Final, 1.0.0.Final
Reporter: Rick-Rainer Ludwig
When defining a timeout in @Test of JUnit Arquillian throws a NullPointerException:
{code}
java.lang.NullPointerException
at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263)
at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOfTimeout.java:62)
{code}
The code to reproduce this:
{code}
import org.jboss.arquillian.junit.Arquillian;
import org.junit.Test;
import org.junit.runner.RunWith;
@RunWith(Arquillian.class)
public class TestTimeout {
@Test(timeout = 3000)
public void test() throws Exception {
Thread.sleep(1000);
}
}
{code}
--
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
12 years
[JBoss JIRA] (ARQ-824) Verify Arquillian can run on JDK 1.5
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-824:
---------------------------------
Summary: Verify Arquillian can run on JDK 1.5
Key: ARQ-824
URL: https://issues.jboss.org/browse/ARQ-824
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.CR7
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Final
Setting compiler options target/source to 1.5 is not enough to verify that the code can actually run on JDK 1.5 since it ignores API changes. To avoid forcing developers to have JDK 1.5 installed to compile, we can add e.g. the Animal Sniffer Maven Plugin to verify using usage of JDK based on known api signatures.
--
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
12 years