[jira] Updated: (WICKET-1638) Wickets unique IDs cause problems for automated testing

["Frank Bille Jensen (JIRA)" <ji...@apache.org>]

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

Frank Bille Jensen updated WICKET-1638:
---------------------------------------

    Fix Version/s:     (was: 1.4-RC1)
                       (was: 1.3.5)

> Wickets unique IDs cause problems for automated testing
> -------------------------------------------------------
>
>                 Key: WICKET-1638
>                 URL: https://issues.apache.org/jira/browse/WICKET-1638
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: John Ray
>            Assignee: Igor Vaynberg
>         Attachments: UniqueIDs.patch
>
>
> Wickets unique markup IDs cause problems writing automated tests. 
> They should be changed so that the first instance of a component with an ID of "foo" on a page would have a generated ID of "foo", the second would be "foo2" and so on. This would make the IDs consistent enough that they could be used for testing.
> See the following discussion for more info.
> http://www.nabble.com/Wickets-unique-IDs-cause-problems-for-Selenium-td17267339.html

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