Thanks Tim;
I have applied your patch to trunk as revision 26357 (I do not have a
check out of 2.3.x here to apply it to). I am going to turn your "no
number converting" flag to on
for trunk - because on trunk we can handle it.
The developers guide, and the code base has alots of examples of test
cases .... really it comes down to writing a method
> publix void testXXXX() throws Exception {
> String expected ="1201011010004500000";
> ....
> Object actual = literal.evaulate( null );
> assertEquals( "check", expected, actual );
> }
And inside the method you can do what ever you want to confirm that your
code (the SAX parser in this case) works.
\Tim Englich wrote:
> Hello Jody,
>
> I create the patch using the Eclipse Team==>C26357reatePatch Method.
> The problem might be that we also use cvs in Eclipse.
>
> I didn't found the correct position to place a testcase so I test it using
> our application TestSzenario.
>
> What I have done.
>
> Creating a new Constructor in FilterFilter where you can set that no
> Number-Converting should done.
> Put this information down to the ExpressionSAXParser.message(...) Method.
>
> When you are using the "normal" constructor everything should work as before.
>
> Is there any tutorial where i could see how to set up a TestCase?
>
> -Tim
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
