Hi Langdon,
I have run into this before as well. You are correct that there is no
method on the jWebUnit API that allows you to specify a list of arguments
to substitute into a property file entry before comparison. But you can
still test this without hardcoding the value of the message and arguments.
Build a string in your testcase by referencing the property entry and
substituting in the argument(s), then call the jWebUnit method that takes a
string rather than a property key.
It would be a useful convenience method on jWebUnit to allow the argument
list as a parameter for those methods that take property keys. You can log
it as an enhancment request if you like - but you should be able to work
around it as above.
cheers,
Jim
> ...
> For instance: errors.integer = {0} must be an integer.
>
> {0} will be replaced when the message is compiled with the field name
> that it applys to.
>
> JWebUnit does not appear to allow me to specify argument values (usually
> other property file keys) to insert into a particular error message. I
> have scoured the documentation and can see no sign that this is possible.
>
> Would someone be able to confirm that this is the case?
>
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Jwebunit-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jwebunit-users
