db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dyre.Tjeldv...@Sun.COM
Subject Re: [jira] Updated: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.
Date Tue, 22 Nov 2005 22:23:28 GMT
>>>>> "DWVC" == David W Van Couvering <David.Vancouvering@Sun.COM> writes:

    DWVC> Yes, I suppose it could use TestRunner directly, but that's not what the 
    DWVC> harness does today, it only works with main routines.  Are you 
    DWVC> suggesting that be changed?

Well, no if there is a good reason for using a main method, I guess
that's ok. It's just that it is a deviation from the standard JUnit
cookbook (or so it seems to me, and I'm a Junit newbie), so it is yet
another thing that has to be documented and remembered...

    >> Should it be possible to run CompatibilitySuite with
    >> junit.swingui.TestRunner? It does not work for me. I get an NPE...

    DWVC> Got me on that one. Rick?

This illustrates another problem with deviating from common JUnit
practice: I works in the harness, but you may not be able to use other
utilities developed for Junit...

    >>> - Add your test to a test suite (e.g. derbylang)
    >> Will that not make it part of derbyall? Do we really want all
    >> bugfix-regression-unit tests to be run in derbyall?

    DWVC> Well, that's your choice, it seems to me in general bugfix unit tests 
    DWVC> should be part of some kind of regression test, and as far as I know 
    DWVC> derbyall is all we have.

Hmm, yes I see your point, but derbyall already takes a long time,
doesn't it?


View raw message