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

["Robert Zeigler (JIRA)" <ji...@apache.org>]

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

Robert Zeigler closed TAP5-161.
-------------------------------

    Resolution: Fixed

This has largely been resolved for real. When I fixed TAP5-1408 and TAP5-1409, I wrote a couple of fairly extensive tests for the component, including making sure that the proper date is selected in the popup, selecting a date in the popup puts the proper date in the text field, etc.  Any further tests will need to be written on a case-by-case basis: as a bug crops up, we add a new test.

> 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
>            Assignee: Robert Zeigler
>             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