RE: [Dunit-interest] Unit testing Delphi Bug List

[Morris, C. <ChrisM@SNELLINGCORP.COM>]

> > Think about if/when we have 680-some tests running, then 
> DUnit is changed
> in
> > some big or small way that affects some or all of the unit tests
> (hopefully,
> > that wouldn't happen, but ...), I wouldn't want the DUnit 
> project burdened
> > with the task of making sure all those tests get updated 
> ... I think it
> > should be separate.
> 
> I just see this as part of the XP challenge.  All tests must 
> run 100% all
> the time. IF the tests don't run (or compile) the code ain't done.

One interesting aspect of Jeremomus is that most of the tests *won't* pass
... or should we code the unit tests to pass, meaning the bug exists? <g>
... Hmmm, I don't think so.

But, if the goal is to write a unit test exposing a bug, how do we make sure
the test is failing due to the bug and not due to some side-effect? That's
maybe a wacky one there. Or is it just -- "make sure you do it right"?

Back to the separate v. same issue ... would you distribute the bug list
test suite with DUnit if you kept them the same? This just feels weird to me
-- "here's DUnit, and an extremely large test suite of the Delphi Bug List"
-- and this weirdness jives with my feeling it should be a separate project.
What do you think about that?

Juanco, what do you think about this issue?

Of course, we could use the DUnit sourceforge resources and keep the test
suite a separate distribution. I'd be more comfortable with that -- keeping
the two separate within the same project...

I dunno, though -- I still think the new project should freeze the DUnit
version it works with and not add that into the mix simply because I don't
think we'll be able to pour a lot of time into it. If we were all working 40
hrs / week on the project, we could absorb any framework changes more
easily, but I think that's too risky given our limited time (especially if
you and I are the only one's who ever get interested in this project <g>). 

Then again, we could still freeze the DUnit version used by Loki-Olen and
not setup a separate project. Really, those are two distinct issues, aren't
they? 

Chris