From: Kristofer S. [SSBV] <K....@ss...> - 2015-01-09 10:50:13
|
I am certainly curious what DUnitX has to offer, so will have a look into that! I think DUnit "died" when CodeGear/Embarcadero integrated it in the Delphi distribution. With all good intentions, but there have been many Delphi language enhancements since DUnit was integrated and therefore CodeGear/Embarcadero has had to bear the brunt of the maintenance effort. Also the DUnit is mature and feature complete up to a certain level. Maybe the GUI Testrunner could be more productive with some of the features mentioned by others, but honestly I don't use the GUI testrunner much anyway - my tests are now 99% console mode based, running on a build server. All of my testing is still based on the 'official' DUnit that ships with Delphi. I have developed my own generic TTestCase descendant class with some extension functions, so I don't feel limited by the lack of new features in DUnit. Actually I very much like the fact that DUnit is so stable (call it "dead" if you like), and that I don't have to continuously rework my tests because of shifts in the test framework. best regards, Kristofer |
From: Warren P. <war...@gm...> - 2015-01-12 20:21:17
|
Reply to Kristofer: API Stability is good. exactly the reason why I'm not dumping DUnit for DUnit/X. But... 1. Don't you wish you could use the GUI test runner to go to the source code of a failing test? 2. Don't you wish you could go from the opened unit in the IDE (MyUnitTestCase333.pas) to that same unit node in the running project (either via searching, or some process better than blind hunting?) Warren On Fri, Jan 9, 2015 at 5:37 AM, Kristofer Skaug [SSBV] <K....@ss...> wrote: > I am certainly curious what DUnitX has to offer, so will have a look into > that! > > I think DUnit "died" when CodeGear/Embarcadero integrated it in the Delphi > distribution. With all good intentions, but there have been many Delphi > language enhancements since DUnit was integrated and therefore > CodeGear/Embarcadero has had to bear the brunt of the maintenance effort. > Also the DUnit is mature and feature complete up to a certain level. Maybe > the GUI Testrunner could be more productive with some of the features > mentioned by others, but honestly I don't use the GUI testrunner much > anyway - my tests are now 99% console mode based, running on a build server. > > All of my testing is still based on the 'official' DUnit that ships with > Delphi. I have developed my own generic TTestCase descendant class with > some extension functions, so I don't feel limited by the lack of new > features in DUnit. Actually I very much like the fact that DUnit is so > stable (call it "dead" if you like), and that I don't have to continuously > rework my tests because of shifts in the test framework. > > best regards, > > Kristofer > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > www.gigenet.com > _______________________________________________ > Dunit-interest mailing list > Dun...@li... > https://lists.sourceforge.net/lists/listinfo/dunit-interest > |