Re: Tests

[Fred Kiefer]

Thank you for your update for 64bit machines now a lot more tests pass. 
Still too much errors to start testing on MacOSX.

Checking for presence of test subdirectories ...
--- Running tests in CFArray ---
--- Running tests in CFCalendar ---
--- Running tests in CFLocale ---

CFLocale/values.m:
Failed file:     values.m aborted without running all tests!
--- Running tests in CFNumber ---
--- Running tests in CFNumberFormatter ---

CFNumberFormatter/format.m:
Failed test:     format.m:60 ... Double formatted correctly
--- Running tests in CFRuntime ---
--- Running tests in CFString ---

CFString/format.m:
Failed test:     format.m:28 ... Float/Doubles are formatted correctly
--- Running tests in CFTimeZone ---
--- Running tests in CFURL ---

CFURL/create.m:
Failed test:     create.m:27 ... Windows style file URL C:\WINDOWS is 
file://localhost/C:%5CWINDOWS/
Failed test:     create.m:30 ... Resource specifier of C:\WINDOWS is 
//localhost/C:%5CWINDOWS/
Failed test:     create.m:33 ... File system path is C:\WINDOWS\
Failed test:     create.m:45 ... File URL /usr is file://localhost/usr/
Failed test:     create.m:48 ... Resource Specifier of /usr is 
//localhost/usr/
Failed test:     create.m:91 ... Strict path of 
http://www.w3.org/silly-file-name is silly-file-name
--- Running tests in CFUUID ---

    154 Passed tests
      8 Failed tests
      1 Failed file
      1 Dashed hope




On 23.01.2012 16:09, Fred Kiefer wrote:
> I did not get around to test your code on MacOSX, but tried to do so on
> my 64bit OpenSuse 12.1 with gcc 4.6.
> First I had to set a few environment variable to get the test to compile
> without installing corebase. You could copy code for that from the base
> GNUmakefile. It would also be great to be able to run make check
> directly from the main directory.
>
> Next I did get a lot of compiler warnings from the CFArray tests.
>
> and finally a lot of the tests failed. For details see the attached
> test.log. Her the test output:
>
> Checking for presence of test subdirectories ...
> --- Running tests in CFArray ---
>
> CFArray/create.m:
> Failed test: create.m:18 ... Found 1 occurence of the value.
> Failed test: create.m:21 ... Found value.
>
> CFArray/mutablearray.m:
> Failed test: mutablearray.m:31 ... Array sorted correctly.
> --- Running tests in CFCalendar ---
>
> CFCalendar/basic.m:
> Failed test: basic.m:18 ... Absolute time composed correctly.
> --- Running tests in CFLocale ---
>
> CFLocale/values.m:
> Failed file: values.m aborted without running all tests!
> --- Running tests in CFNumber ---
> --- Running tests in CFNumberFormatter ---
>
> CFNumberFormatter/format.m:
> Failed test: format.m:60 ... Double formatted correctly
> --- Running tests in CFRuntime ---
> --- Running tests in CFString ---
>
> CFString/format.m:
> Failed test: format.m:28 ... Float/Doubles are formatted correctly
> --- Running tests in CFTimeZone ---
> --- Running tests in CFURL ---
>
> CFURL/create.m:
> Failed test: create.m:27 ... Windows style file URL C:\WINDOWS is
> file://localhost/C:%5CWINDOWS/
> Failed test: create.m:30 ... Resource specifier of C:\WINDOWS is
> //localhost/C:%5CWINDOWS/
> Failed test: create.m:33 ... File system path is C:\WINDOWS\
> Failed test: create.m:45 ... File URL /usr is file://localhost/usr/
> Failed test: create.m:48 ... Resource Specifier of /usr is //localhost/usr/
> Failed test: create.m:91 ... Strict path of
> http://www.w3.org/silly-file-name is silly-file-name
>
> CFURL/ref_resolution.m:
> Failed test: ref_resolution.m:41 ... ./g resolved against
> http://a/b/c/d;p?q is http://a/b/c/g
> Failed test: ref_resolution.m:69 ... ../.. resolved against
> http://a/b/c/d;p?q is http://a/
> Failed test: ref_resolution.m:76 ... ../../g resolved against
> http://a/b/c/d;p?q is http://a/g
> Failed test: ref_resolution.m:83 ... ../../../../g resolved against
> http://a/b/c/d;p?q is http://a/g
> Failed test: ref_resolution.m:90 ... /./g resolved against
> http://a/b/c/d;p?q is http://a/g
> Failed test: ref_resolution.m:97 ... /../g resolved against
> http://a/b/c/d;p?q is http://a/g
> Failed test: ref_resolution.m:111 ... ./../g resolved against
> http://a/b/c/d;p?q is http://a/b/g
> --- Running tests in CFUUID ---
>
> 143 Passed tests
> 19 Failed tests
> 1 Failed file
>
>
> Some testing was abandoned when a test program aborted. This is
> generally a severe problem and may mean that the package is
> completely unusable. You need to try to fix this and, if it is
> not due to some problem on your system, please help by submitting
> a patch (or at least a bug report) to the package maintainer.
>
> One or more tests failed. None of them should have.
> Please submit a patch to fix the problem or send a bug report to
> the package maintainer.
>
> On 23.01.2012 15:43, Stefan Bidi wrote:
> > It has been a week and I have not gotten any feedback, one way or
> > another.
> > I would really appreciate if people interested on the project to could
> > please test it. The priority right now is to verify that the tests are
> > correct. Running these tests on OS X and reporting back would do that. I
> > understand the core libraries are getting scrubbed now and that is taking
> > up most of the available time, but this should only take a few minutes.
> >
> > Thanks
> >
> > On Mon, Jan 16, 2012 at 8:38 PM, Stefan Bidi<stefanbidi@gmail.com> wrote:
> >
> > > I do not have a machine with OS X installed, so I'm a bit at a
> > > disadvantage when it comes to writing tests. To prepare for the 0.1
> > > release of corebase, I'd like to make sure the tests in the test
> > > suite are
> > > correct and that they test things people are actually using. I would
> > > really appreciate if people could run the test suite on OS X and report
> > > back, patches would be nice. If you have commit access to SVN, feel free
> > > commit changes yourself. If you have a particular use case, new tests
> > > would be even more welcome.
> > >
> > > Really, anything would be helpful. For CFURL, for example, I just ported
> > > some tests from the base test suite (it fails a bunch of stuff, but
> > > it's a
> > > start).
> > >
> > > Thanks

tests.log
Description: Text Data