[
https://issues.apache.org/jira/browse/WICKET-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Rantalaiho updated WICKET-254:
-----------------------------------
Affects Version/s: (was: 2.0)
1.3
I ported the quickstart to the current 1.3.0 snapshot, but the behaviour
remains the same (quickstart works, but the unit test fails).
Now after getting a bit more Wicket experience I started to think that maybe
the validation works in a way which makes testing difficult. I've been having
hard time testing any ajax field validations with WicketTester. In the case of
a normal form submit the test is easier to do if you can test e.g. the presence
of an error message on the screen after doing submit with FormTester.
> WicketTester does not toggle isValid() of a single, ajax-validated form field
> -----------------------------------------------------------------------------
>
> Key: WICKET-254
> URL: https://issues.apache.org/jira/browse/WICKET-254
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3
> Environment: Ubuntu Dapper Linux, Sun java 1.5.0_10
> Reporter: Timo Rantalaiho
> Attachments: ajax-validation-sans-submit-1.3.0.zip,
> ajax-validation-sans-submit.zip
>
>
> I have code to validate {{TextField}}s one by one with ajax. While the code
> works, I wasn't able to assert it working with WicketTester.
> The attached quickstart can be used to reproduce the problem on a 2.0
> snapshot. The code works in a browser (validity gets toggled true / false
> when changing the input length), but WicketTester fails.
> With WicketTester, the ajax event gets triggered (and it calls {{validate}}
> on the field), but {{isValid}} always returns {{true}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
