[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, 1 month
[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, 1 month
[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, 1 month
[JBoss JIRA] Created: (ARQ-77) Support @EJB injection
by Andrew Lee Rubinger (JIRA)
Support @EJB injection
-----------------------
Key: ARQ-77
URL: https://jira.jboss.org/jira/browse/ARQ-77
Project: Arquillian
Issue Type: Feature Request
Components: OpenEJB Containers
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Tests should be able to have class or instance members injected according to @EJB semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible resolvers (which need an EJB name, module name, app name, and business interface name). Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month