You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/10/21 01:28:50 UTC

[jira] Created: (TAPESTRY-1844) Devise test stategy for DateField and other DHTML/JS intensive components

Devise test stategy for DateField and other DHTML/JS intensive components
-------------------------------------------------------------------------

                 Key: TAPESTRY-1844
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1844
             Project: Tapestry
          Issue Type: Task
    Affects Versions: 5.0.5
            Reporter: Howard M. Lewis Ship


The new DateField component is difficult to test inside Selenium because Selenium doesn't track what occurs after the user clicks the trigger button. Not sure how to make that work, it may require an upgrade to a newer version of selenium.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

[jira] Commented: (TAPESTRY-1844) Devise test stategy for DateField and other DHTML/JS intensive components

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629329#action_12629329 ] 

Howard M. Lewis Ship commented on TAPESTRY-1844:
------------------------------------------------

Made some progress on this:

http://tapestryjava.blogspot.com/2008/08/ajax-and-selenium-waitforcondition.html

> Devise test stategy for DateField and other DHTML/JS intensive components
> -------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1844
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1844
>             Project: Tapestry
>          Issue Type: Task
>    Affects Versions: 5.0.5
>            Reporter: Howard M. Lewis Ship
>
> The new DateField component is difficult to test inside Selenium because Selenium doesn't track what occurs after the user clicks the trigger button. Not sure how to make that work, it may require an upgrade to a newer version of selenium.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

[jira] Commented: (TAPESTRY-1844) Devise test stategy for DateField and other DHTML/JS intensive components

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617967#action_12617967 ] 

Howard M. Lewis Ship commented on TAPESTRY-1844:
------------------------------------------------

http://agiletesting.blogspot.com/2006/03/ajax-testing-with-selenium-using_21.html


> Devise test stategy for DateField and other DHTML/JS intensive components
> -------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1844
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1844
>             Project: Tapestry
>          Issue Type: Task
>    Affects Versions: 5.0.5
>            Reporter: Howard M. Lewis Ship
>
> The new DateField component is difficult to test inside Selenium because Selenium doesn't track what occurs after the user clicks the trigger button. Not sure how to make that work, it may require an upgrade to a newer version of selenium.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

[jira] Commented: (TAPESTRY-1844) Devise test stategy for DateField and other DHTML/JS intensive components

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621112#action_12621112 ] 

Howard M. Lewis Ship commented on TAPESTRY-1844:
------------------------------------------------

I believe Seleniums' waitForCondition is used to handle this situation.

> Devise test stategy for DateField and other DHTML/JS intensive components
> -------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1844
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1844
>             Project: Tapestry
>          Issue Type: Task
>    Affects Versions: 5.0.5
>            Reporter: Howard M. Lewis Ship
>
> The new DateField component is difficult to test inside Selenium because Selenium doesn't track what occurs after the user clicks the trigger button. Not sure how to make that work, it may require an upgrade to a newer version of selenium.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org