db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jakob Braeuchi <jbraeu...@gmx.ch>
Subject Re: JUnit Tests fail
Date Wed, 26 Nov 2003 16:39:59 GMT
hi all,

sorry, i didn't see those :(
i'll have to change some parts of the paging because it currently 
requires defined start and end indices whereas the testcases only use a 
start index.

jakob

Armin Waibel wrote:
> Hi Robert,
> 
> the junit result files of the ant target
> are in db-ojb/target/test/junit-XYZ.txt
> 
> I get the same 3 failures in ODMG test part.
> Think these test failures are a result of the
> new paging mechanism. I'm sure that Jakob will
> fix this ASAP.
> 
> regards,
> Armin
> 
> Robert S. Sfeir wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Oliver,
>> Glad to see I'm not the only one :-)
>>
>> perhaps the commiters are used to some of these failures, but a new
>> commer like myself will get very confused.
>>
>> Some of the error I get related to the fact that some of the ojb xml
>> files fail the parsing process.
>>
>> I am going to setup IDEA tonight to run those JUnit tests, I'll setup a
>> test suite and see what falls apart.  This way I can report the exact
>> methods and exact complaints I get.  I like ant to run anything, but for
>> JUnit tests I don't yet because it's too much of a black box, stuff
>> happens and unless you accounted for it, you don't know that it happened.
>>
>> R
>>
>> oliver.matz@ppi.de wrote:
>> | Hello Robert,
>> |
>> | the junit tests suite is sub-optimal, I agree.
>> |
>> |
>> |>-----Original Message-----
>> |
>> |
>> |>Can't run JUnit tests, either I have something wrong or someone hasn't
>> |>clicked run the junit test by itself in a while or something.
>> |
>> |
>> | [..]
>> |
>> |
>> |>Failed to execute: ECHO Not implemented
>> |>java.sql.SQLException: Unexpected token: ECHO in statement [ECHO Not
>> |>implemented]
>> |>0 of 1 SQL statements executed successfully
>> |
>> |
>> | that is o.k.  I have not understood what this is good for,
>> | but you can ignore that.
>> |
>> | [..]
>> |
>> |
>> |>[BOOT] INFO: No value for key 'CollectionProxyClass'
>> |
>> |
>> | I noticed that message, too.
>> |
>> |
>> |>Tests run: 167, Failures: 3, Errors: 0, Time elapsed: 14.16 sec
>> |
>> |
>> | Sometimes tests fail at my side, too.  I even have
>> | non-determinsitic test failures.  It is really annoying.
>> | I had a look at it, but they are Heisenbugs: when you try
>> | to localize them, they do not appear.
>> |
>> | Which are the tests that fail?  (You may use ant target
>> | junit-report to get an html-report if you like that.)
>> |
>> | See also thread
>> | "non-deterministic test failures, was: RE: junit test failures"
>> |
>> | We need to
>> |
>> | (1) get rid of the non-determinism and
>> |
>> | (2) find a policy to deal with tests that fail because they
>> |     exihibit known problems.
>> |
>> | Olli
>> |
>> | ---------------------------------------------------------------------
>> | To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> | For additional commands, e-mail: ojb-dev-help@db.apache.org
>> |
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.3 (MingW32)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>> iD8DBQE/w07p+cV9vuB27SARAm9JAKDv8xohlroQlg9HUB79wy1/OOaNiwCfZZHI
>> f/HN3TDWzLTBGD43QXYs3qg=
>> =WEcX
>> -----END PGP SIGNATURE-----
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
>>
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Mime
View raw message