[JBoss JIRA] (ARQGRA-236) Made @FindBy annotation lookup mechanism extensible
by Lukáš Fryč (JIRA)
Lukáš Fryč created ARQGRA-236:
---------------------------------
Summary: Made @FindBy annotation lookup mechanism extensible
Key: ARQGRA-236
URL: https://issues.jboss.org/browse/ARQGRA-236
Project: Arquillian Graphene
Issue Type: Enhancement
Reporter: Lukáš Fryč
Assignee: Juraj Húska
Priority: Minor
Fix For: 2.0.0.Alpha3
Consider following:
{code:java}
@FindByJSF("button")
WebElement loginButton;
@WebElementLookup(strategy=JSFLookupStrategy.class)
public @interface FindByJSF {
public String value() default INFER;
}
{code}
This way, extensions could bring custom lookup strategies, e.g. connected to framework capabilities.
--
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, 9 months
[JBoss JIRA] (ARQ-1243) Warp: allow finding elements by JSF ids - @FindByJSF (Graphene integration)
by Lukáš Fryč (JIRA)
Lukáš Fryč created ARQ-1243:
-------------------------------
Summary: Warp: allow finding elements by JSF ids - @FindByJSF (Graphene integration)
Key: ARQ-1243
URL: https://issues.jboss.org/browse/ARQ-1243
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha2
Reporter: Lukáš Fryč
Consider following:
{code:java}
@FindBy(id = "form:loginPanel:loginButton")
WebElement loginButton;
@FindByJSF("loginButton")
WebElement loginButton;
// when the locator will be automatically inferred from field name
@FindByJSF
WebElement loginButton;
@FindByJSF
Calendar calendar;
{code}
This will need to allow Graphene test enricher to consume arbitrary annotations - e.g. annotations annotated with @FindCapable providing custom lookup strategy.
--
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, 9 months
[JBoss JIRA] (ARQGRA-213) print contextpath and option to sleep after starting the @Deployment
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-213?page=com.atlassian.jira.plugin... ]
Lukáš Fryč commented on ARQGRA-213:
-----------------------------------
I propose another principle - leave the deployment deployed and undeploy it during deployment of next deployment.
This will be so called development mode which will allow inspection of the page after test.
This can be already achieved using {{arquillian-jrebel-extension}}.
> print contextpath and option to sleep after starting the @Deployment
> --------------------------------------------------------------------
>
> Key: ARQGRA-213
> URL: https://issues.jboss.org/browse/ARQGRA-213
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Reporter: Mark Struberg
> Assignee: Lukáš Fryč
> Fix For: 2.0.0.Alpha3
>
>
> Most graphene unit test have a @Deployment section and something similar to the following:
> {code}
> @ArquillianResource
> private URL contextPath;
> {code}
> When debugging the Server for finding the bug in the webapp it's often needed to manually click through the application and invoke requests directly. But to do that you need the contextpath! It would be nice if Arquillian Graphene would log this information.
> Another highly useful feature would be to stop the test after a @Deployment via a -D java option. Currently I need to add a Thread.sleep(600000L) to my test manually if I like to test the server. If I don't do that Selenium aborts the test with a failure after 30s if I'm debugging the server.
--
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, 9 months
[JBoss JIRA] (ARQGRA-213) print contextpath and option to sleep after starting the @Deployment
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-213?page=com.atlassian.jira.plugin... ]
Lukáš Fryč commented on ARQGRA-213:
-----------------------------------
[~kpiwko], the development mode leaving deployment deployed after test could be actually part of Drone, wdyt?
> print contextpath and option to sleep after starting the @Deployment
> --------------------------------------------------------------------
>
> Key: ARQGRA-213
> URL: https://issues.jboss.org/browse/ARQGRA-213
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Reporter: Mark Struberg
> Assignee: Lukáš Fryč
> Fix For: 2.0.0.Alpha3
>
>
> Most graphene unit test have a @Deployment section and something similar to the following:
> {code}
> @ArquillianResource
> private URL contextPath;
> {code}
> When debugging the Server for finding the bug in the webapp it's often needed to manually click through the application and invoke requests directly. But to do that you need the contextpath! It would be nice if Arquillian Graphene would log this information.
> Another highly useful feature would be to stop the test after a @Deployment via a -D java option. Currently I need to add a Thread.sleep(600000L) to my test manually if I like to test the server. If I don't do that Selenium aborts the test with a failure after 30s if I'm debugging the server.
--
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, 9 months
[JBoss JIRA] (ARQGRA-200) Enhance Graphene's guards to wait until page fully updates
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-200?page=com.atlassian.jira.plugin... ]
Lukáš Fryč edited comment on ARQGRA-200 at 12/12/12 4:51 AM:
-------------------------------------------------------------
We need to write extensive ftests to cover this issue.
Test what happens when someone setups asynchronous callback (setTimeout) in AJAX response.
was (Author: lfryc):
We need to write extensive ftests to cover this issue.
> Enhance Graphene's guards to wait until page fully updates
> ----------------------------------------------------------
>
> Key: ARQGRA-200
> URL: https://issues.jboss.org/browse/ARQGRA-200
> Project: Arquillian Graphene
> Issue Type: Enhancement
> Affects Versions: 2.0.0.Alpha2
> Reporter: Jiří Štefek
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 2.0.0.Alpha3
>
>
> It would be nice if Graphene's guards (guardXhr, guardHttp and guardNoRequest) can be used to wait until page fully updates after the the request.
--
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, 9 months