Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Message-ID: <3E4CE093.1040600@cyberspaceroad.com>
Date: Fri, 14 Feb 2003 13:26:59 +0100
From: Adam Hardy <adam.ant@cyberspaceroad.com>
Reply-To: user@ant.apache.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
MIME-Version: 1.0
To: Ant Users List <user@ant.apache.org>
Subject: Re: AW: AW: running junit on ant source
References: <879A5AD5DD0ED511891F0003473A9B5603CCC272@Z011004>
In-Reply-To: <879A5AD5DD0ED511891F0003473A9B5603CCC272@Z011004>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

I've now got a failure on fixcrlf test itself.

Same issue. On test3 where it tests the replacement of tabs, the 
'expected' file has got an extra 12 bytes, which is exactly how many 
lines it's got.

The fix would be to put fixcrlf in the target first on the input and 
expected files to make sure they are OS compatible.

However since fixcrlf is being tested itself, I'm not quite sure about 
the integrity of using it to process its own test files before running 
its test, assuming I will submit the fix to the source.

I'm new to JUnit. I'd appreciate some guidance here.


Jan.Materne@rzf.fin-nrw.de wrote:
> The test build.xml is one directory over the "expected":
> src\etc\testcases\filters\build.xml
> 
> 
> Jan Mat�rne
> 
> -----Urspr�ngliche Nachricht-----
> Von: Adam Hardy [mailto:adam.ant@cyberspaceroad.com]
> Gesendet am: Freitag, 14. Februar 2003 11:06
> An: Ant Users List
> Betreff: Re: AW: running junit on ant source
> 
> No I'm using Linux. I haven't figured out how to make emacs show CRLF 
> symbols visibly, but the file sizes are different.
> 
> The file in expected is 27 bytes, but the one generated in result is 26 
> bytes.
> 
> The original input with three lines in is also has the extra CRs in.
> 
> I guess somebody fixed the files for windows, and now it doesn't work 
> for Linux!
> 
> Unfortunately emacs preserves whatever end-of-line character is there 
> when I save.
> 
> I fixed the test case build.xml by using fixcrlf as you suggested. I put
> 
> <fixcrlf srcdir="input"/>
> <fixcrlf srcdir="expected"/>
> 
> in the test target, and it executes OK now.
> 
> Do you think the test build.xml is in the source database? Sorry I 
> haven't looked that far yet. I'll try submitting it when I get through 
> the other tests (Another one just failed). Well spotted, by the way. I 
> would have poured over the source code for ages before looking at the CRLFs!
> 
> 
> 
> 
> 
> Jan.Materne@rzf.fin-nrw.de wrote:
> 
>>I had the same.
>>Do you work on windows?
>>
>>If you have a look at src\etc\testcases\filters\expected\linecontains.test
>>it contains unixlike line separators. The generated file (very short time
> 
> in
> 
>>src\etc\testcases\filters\result\linecontains.test) has - because running
> 
> on
> 
>>windows - windowslike line separators. And they are different, so the test
>>fail.
>>
>>Maybe there should be a solution by inserting a <fixcrlf> in the main
> 
> build
> 
>>file. But a workaround is to <fixcrlf> in your local source or do that
> 
> with
> 
>>an editor (I opened that an on resave a got the windows line sep�s).
>>
>>
>>Jan Mat�rne
>>
>>-----Urspr�ngliche Nachricht-----
>>Von: Adam Hardy [mailto:adam.ant@cyberspaceroad.com]
>>Gesendet am: Donnerstag, 13. Februar 2003 17:36
>>An: user >> Ant Users List
>>Betreff: running junit on ant source
>>
>>I'm doing some mods to two of the ant source classes, and I'm following 
>>the guidelines from the ant docs about running tests under junit and 
>>creating new tests.
>>
>>I'm new to junit today actually and I'm using "ant run-tests" in the ant 
>>home directory to make sure all the junit tests that come with the 
>>source code work.
>>
>>I get this failure on the first testcase junit comes to and I don't know 
>>what it means. Is it obvious to anyone what's wrong here? I presume the 
>>problem lies with my set-up, because according to junit, I should get 
>>more info when a test fails - I presume that the "null" here would 
>>normally be a line or 2 about what failed:
>>
>>     [junit] Testcase: 
>>testLineContains(org.apache.tools.ant.filters.LineContainsTest):  FAILED
>>     [junit] null
>>     [junit] junit.framework.AssertionFailedError
>>
>>
>>Thanks if you can help,
>>Adam
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>>For additional commands, e-mail: user-help@ant.apache.org
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>