Hi Jeffry, > > Or you can create an integration unit test. Extend ServletTestCase > and use cactus to perform an in-container test with t2. I'd like to echo > James comment, unit tests will always help understanding and getting > patches looked at faster. >
I have already have a testcase, which I am expanding now ;). It just seams a waste (of at least my time) at the moment, to setup a running turbine for this simple functionality. I will try to see if it runs anyway in the integration test or the normal test cases, when I know for sure that the current testcase is resulting in correct values. While we are at it : DataStreamParser is reusing the same object over and over again, which causes my tests to fail ;). It just maintains the last values read from the csv file. What I am doing in my testcase is actually storing all BaseValueParser objects in a vector and after that compare values and fail the test when necessary. So I would like to change that behaviour in creating a new object everytime a new "record" is read. The question however is if the user at any point able to do so, when using this parser (don't have a clue where this CSVParser can be actually used). Sorry about my lack of knowledge of turbine, but since fixing things is my way of learnign what is underneath, I like it that way ;) Call it strange, but strange is my name ;) Thanx for the input btw.. I will resubmit the java files and submit the test I wrote, working under the current test "containers" that are available (that is src/rttest or src/test.. Mvgr, Martin van den Bemt -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
