[JBoss JIRA] (ARQ-1609) Allow setting IE driver path in arquillian.xml configuration
by Oliver Kišš (JIRA)
Oliver Kišš created ARQ-1609:
--------------------------------
Summary: Allow setting IE driver path in arquillian.xml configuration
Key: ARQ-1609
URL: https://issues.jboss.org/browse/ARQ-1609
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Drone
Affects Versions: drone_1.2.1.Final
Reporter: Oliver Kišš
Currently, path to IE driver executable can be set by {{webdriver.ie.driver}} system property. It would be more convenient if the path could also be configured in {{arquillian.xml}}.
--
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
[JBoss JIRA] (ARQGRA-416) @InFrame duplicitly switches to iframe with fragment method
by Jan Dosoudil (JIRA)
Jan Dosoudil created ARQGRA-416:
-----------------------------------
Summary: @InFrame duplicitly switches to iframe with fragment method
Key: ARQGRA-416
URL: https://issues.jboss.org/browse/ARQGRA-416
Project: Arquillian Graphene
Issue Type: Bug
Affects Versions: 2.0.0.Final
Reporter: Jan Dosoudil
{code}
public class Fragment {
@FindBy(id="button")
private WebElement button;
public void clickButton() {
button.click();
}
public WebElement getButton() {
return button;
}
}
{code}
{code}
@RunWith(Arquillian.class)
@RunAsClient
public class Test {
//...
@FindBy(id="content")
@InFrame(nameOrId="frame")
private Fragment Fragment;
@Test
public void testWebElement() {
fragment.getButton().click(); //PASS
}
@Test
public void testMethod() {
fragment.clickButton(); //FAIL
}
}
{code}
Exception is: org.openqa.selenium.NoSuchFrameException: Unable to locate frame: 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
[JBoss JIRA] (ARQ-1603) tmpDir specification should allow to be without trailing slash
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1603?page=com.atlassian.jira.plugin.s... ]
Karel Piwko resolved ARQ-1603.
------------------------------
Assignee: Stefan Miklosovic
Fix Version/s: droidium_1.0.0.Alpha4
Resolution: Done
> tmpDir specification should allow to be without trailing slash
> --------------------------------------------------------------
>
> Key: ARQ-1603
> URL: https://issues.jboss.org/browse/ARQ-1603
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha3
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
> Fix For: droidium_1.0.0.Alpha4
>
>
> *Given*:
> I define tmpDir like "C:\temp" or /tmp
> *Then*:
> Droidium creates a temp directory like C:\temp-1223-1454-1245-12545
> *Expect*:
> I expect directory to be rather C:\temp\1223-1454-1245-12545
> Current behavior is problematic as it requires user to be slash aware as otherwise he might want to create a directory in tree hierarchy where elevated permissions are needed.
> Implemenation note:
> new File(File parent, String childPath) would be the best way how to handle 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
11 years
[JBoss JIRA] (ARQ-1600) ProcessExecutor might get stuck on Windows
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1600?page=com.atlassian.jira.plugin.s... ]
Karel Piwko updated ARQ-1600:
-----------------------------
Status: Resolved (was: Pull Request Sent)
Assignee: Karel Piwko
Fix Version/s: droidium_1.0.0.Alpha4
Resolution: Done
Pushed upstream in https://github.com/arquillian/arquillian-droidium/commit/5dc4d2b21a4466e9...
> ProcessExecutor might get stuck on Windows
> -------------------------------------------
>
> Key: ARQ-1600
> URL: https://issues.jboss.org/browse/ARQ-1600
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha3
> Reporter: Karel Piwko
> Assignee: Karel Piwko
> Priority: Blocker
> Fix For: droidium_1.0.0.Alpha4
>
>
> Current execution of external process on Windows might lead to following issues, causing process deadlock:
> 1/ Process stdin is not closed if no longer needed
> 2/ Process stdout and stderr never reach EOF
> This behavior is observed when a .bat file file is executed on Windows. This behavior is caused by missing file descriptors to underlying process spawned by bat file.
> Implementation note: There are two ways how to resolve the issue.
> * read output stream and consider them finished if specific message is encountered
> * unwrap bat execution and execute directly underlying command
--
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
[JBoss JIRA] (ARQ-1608) Invoke extensions related to AnnotationDeploymentScenarioGenerator in order of deployments
by Robert Panzer (JIRA)
Robert Panzer created ARQ-1608:
----------------------------------
Summary: Invoke extensions related to AnnotationDeploymentScenarioGenerator in order of deployments
Key: ARQ-1608
URL: https://issues.jboss.org/browse/ARQ-1608
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Base Implementation
Affects Versions: 1.1.2.Final
Environment: Win7, Java 6
Reporter: Robert Panzer
Currently there is no order in which for example ProtocolArchiveProcessors are called in case a test class provides multiple deployments.
It would be nice if the extension related to the AnnotationDeploymentScenarioGenerator were called in the same order.
--
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