From: <ju...@su...> - 2001-01-27 22:13:54
|
> Juanco, what do you think about this issue? I like the project very much, and I think it's worth pursuing, but I can't compromise any time to it right now. > 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'd keep it all under the same CVS tree. Knowing that a change to the framework broke the Delphi test suite would be very valuable information. I'd even add the tests, conditionally, to the default build process. As to existing bugs, I think we should test for their presence. IOW, the test case should fail if the bug's not there. We can clear any confusion by placing tests for bugs in a specific part of the hierarchy. Once a bug is fixed, the test case's result can be reversed, and the test moved to another place. The opposite approach, having failure (the bug's there) mean success, seems all too confusing. > 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. Hmm. I don't expect DUnit to change in ways that would make existing test cases so difficult to use. In fact, I'd be happy to maintain the bug suite once is there. As I said, I think that if the suite gets broken, then it will probably be due to a bug in DUnit. I think that placing the bug suite in a different SF module would be fine. SF encourages spawning new projects, but I think that would be too much of a hassle, at least until the bug suite project acquires a life of its own. Besides, it seems that the type of developer that would be interested in DUnit is exactly the same group that would be intereste in the bug suite. Juanco |