You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Massimo Lusetti (JIRA)" <ji...@apache.org> on 2011/08/12 00:08:27 UTC

[jira] [Closed] (TAP5-161) Devise test stategy for DateField and other DHTML/JS intensive components

     [ https://issues.apache.org/jira/browse/TAP5-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Massimo Lusetti closed TAP5-161.
--------------------------------

       Resolution: Won't Fix
    Fix Version/s: 5.3

DateField always cause issues

> Devise test stategy for DateField and other DHTML/JS intensive components
> -------------------------------------------------------------------------
>
>                 Key: TAP5-161
>                 URL: https://issues.apache.org/jira/browse/TAP5-161
>             Project: Tapestry 5
>          Issue Type: Task
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>             Fix For: 5.3
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira