dunit-interest — General discussion about DUnit

[DUnit-interest] TestTextRunner memory leaks

[Веселин Г. <us...@ab...>]

Hi,

I am using DUnit 9.3.0 for a legacy Delphi 7 application. I use primarily TextTestRunner to run the tests. I also use FastMM4 and I noticed memory leaks. These leaks do not happen when I use GUITestRunner. 
I am not sure if this is due to a bug in DUnit or maybe it is some configuration problem.

To reproduce this behavior I created a very simple Delphi 7 project with just one unit:

program FFLeak;

{$APPTYPE CONSOLE}

uses
  FastMM4,
  TestFramework,
  TextTestRunner,
  uBasicTest in 'uBasicTest.pas';

begin
  TextTestRunner.RunTest(TBasicTest.Suite);
end.

{****}

unit uBasicTest;

interface

uses
  TestFramework;

type
  TBasicTest = class (TTestCase)
  published
    procedure BasicTestProc;
  end;

implementation

{ TBasicTest }

procedure TBasicTest.BasicTestProc;
begin
  // dummy procedure
end;

end.


When I run this program, FastMM reports the following:

This application has leaked memory. The small block leaks are (excluding expected leaks registered by pointer):

13 - 20 bytes: TStatusToResultAdapter x 1, TList x 4, TInterfaceList x 2, AnsiString x 1, Unknown x 2
21 - 36 bytes: TThreadList x 2, AnsiString x 1
37 - 52 bytes: TTextTestListener x 1
53 - 68 bytes: TTestResult x 1
85 - 100 bytes: TTestSuite x 1
101 - 116 bytes: TBasicTest x 1

What can be the reason for this? Where should  I look for a problem? Or is it a known behavior?
It doesn't seem to be a problem with how FastMM is configured, because I also ran my tests without it and I could see the test program indeed started to consume more and more memory.

Re: [DUnit-interest] JUnitXMLTestRunner - how to submit?!

[Juancarlo A. <ap...@gm...>]

Carsten,

There's work going on to move DUnit to either Bitbucket or Github.

I'm not involved, so I don't know.

Maybe Jeroen Pluimers?

Cheers,

On Tue, May 26, 2015 at 12:13 PM, Carsten Kuckuk <ck...@ku...> wrote:

> Dear List Members,
>
> Last week I inherited a Delphi7 project, and wanted to put it under Unit
> Tests. I stumbled on DUnit, and it worked like a charm, so thank you for
> this project. I then wanted to integrate it with Jenkins, which loves to
> read JUnit-style XML reports, so I tried out the XMLTestRunner under
> Contrib. That's a nice piece of software, and worked immediately, but
> unfortunately it uses different string constants. So I made a copy of
> it, renamed it, and adapted it to the JUnit XML dialect. I'd like to
> submit that, but I'm not familiar with how this is done here. Could
> somebody please point out to me what I have to do here -- on list or off
> list (ck at kuckuk dot com)?!
>
> Thank you very much in advance!
>
> Regards,
>
> Carsten
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Dunit-interest mailing list
> Dun...@li...
> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>



-- 
Juancarlo *Añez*

[DUnit-interest] JUnitXMLTestRunner - how to submit?!

[Carsten K. <ck...@ku...>]

Dear List Members,

Last week I inherited a Delphi7 project, and wanted to put it under Unit 
Tests. I stumbled on DUnit, and it worked like a charm, so thank you for 
this project. I then wanted to integrate it with Jenkins, which loves to 
read JUnit-style XML reports, so I tried out the XMLTestRunner under 
Contrib. That's a nice piece of software, and worked immediately, but 
unfortunately it uses different string constants. So I made a copy of 
it, renamed it, and adapted it to the JUnit XML dialect. I'd like to 
submit that, but I'm not familiar with how this is done here. Could 
somebody please point out to me what I have to do here -- on list or off 
list (ck at kuckuk dot com)?!

Thank you very much in advance!

Regards,

Carsten

Re: [DUnit-interest] A message from Jeroen Pluimers.

[Juancarlo A. <ap...@gm...>]

On Mon, Jan 12, 2015 at 11:58 AM, Warren Postma <war...@gm...>
wrote:

> *I received this message from Jeroen, who is having trouble posting
> directly to the list:  His email is included in the message below, so reply
> to it off list if you need to.*
>

I'm having trouble logging into Source Forge, both on the main page, and on
the e-mail list page.

I suggest Jeroen moves the list to Google groups.

I'll keep trying to access SF to let users know of the switch to GitHub and
GG.

Cheers,


-- 
Juancarlo *Añez*

Re: [DUnit-interest] Is DUnit dead?

[Warren P. <war...@gm...>]

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
>

[DUnit-interest] A message from Jeroen Pluimers.

[Warren P. <war...@gm...>]

*I received this message from Jeroen, who is having trouble posting
directly to the list:  His email is included in the message below, so reply
to it off list if you need to.*


Hi Everyone,

A long while ago, Juancarlo Añez has made me admin, and I'm finally going
to take on that role.

Knowing I need to balance this tough job with my limited resources,
distributed/cloud based nature of my software development processes, and
with respect to the current and past contributions I plan to do the
following (probably far from complete, but a start):

- import everything into GitHub (in my experience it is the best); I'm
currently experimenting with https://github.com/jpluimers/DUnit-SF
- add readme.md markdown
- introduce GitFlow
- accept push requests from others
- create a pre-Delphi 2007 branch
- limit support to the following Delphi versions: 2007, 2010+ (I don't run
Delphi 2009 as it is too buggy, Delphi 2007 is the first version having
msbuild support)
- provide msbuild builds for the supported Delphi versions
- create an embarcadero branch and include (Delphi version by Delphi
version) the changes that have not been committed since Mark Edington left
Embarcadero into a separate branch
- merge some of the Spring4D FMX contributions into here
https://bitbucket.org/sglienke/spring4d/src/master/Tests/Source/dUnit/
- get a DUnit Wizard into source code or coerce Embarcadero to provide
theirs
- get the FMX GUI from Spring4D and other things
- look at these projects to see what could be included (partially from
http://stackoverflow.com/questions/5136422/what-testing-framework-unit-testing-to-use-with-delphi-xe-starter-edition
 )
    - https://svn.code.sf.net/p/dunit2/code/trunk/ (as
http://github.com/graemeg/dunit2 is dead; need to find out who jarrodh is
and why he's only on the DUnit2 SFT.net project)
    - https://github.com/graemeg/fptest
    -
https://sourceforge.net/p/tiopf/code/ci/7197098d612e80abfc41d4223a624e7efc0a5bf6/tree/3rdParty/DUnit/
- assign the current bugs and find resources to act on them (assess,
reproduce, fix when needed)
- provide better cross platform NUnit XML output than currently in
both DUnit-XML projects (maybe merge the two; I'm very much open for input
on this)
- provide better IDE runner integration than
http://www.tiriss.com/UnitTesting/showinide.html
- adopt the wizard to introduce an optional intermediate layer as mentioned
at http://www.tiriss.com/UnitTesting
- not going into the DUnitX direction as currently it does not map well
from DUnit and does not follow the thoughts in xUnit. A big aim for me is
to be as compatible with current DUnit projects as possible and maintain
the xUnit approach.

I am open to contributions from the FreePascal community, but I'm not an
active FreePascal user.

I need as much help as I can get, but I'm not a real manager: I'm a coder
and geek that is taking on a life long learning job of acquiring human
skills, so bear with me.

Note I'm not heavy into email any more but way more active on G+ and read
stuff through feedly and RSS feeds (which this mailing list does not
support).

It was a painful process taking multiple tries to get subscribed on this
mailing list at all, and no luck in posting (multiple tries with a from
je...@pl... via my gmail address which works fine for other
maillists) so I don't want to spend too much time on it.

Regards, and expecting GitHub to work better (:

--jeroen

Groet,
--
Jeroen W. Pluimers - specialist in .NET, Win32, SQL, Visual Studio & Delphi
tel: +31 20 610 8322
fax: +31 20 610 8323
GSM: +31 654 385 135
mailto:je...@pl...
BeSharp.net is a trademark of Pluimers Software Ontwikkeling BV, Amsterdam,
Trade-register 34152606
http://wiert.me ; http://jwpluimers.myplaxo.com/

Re: [DUnit-interest] Is DUnit dead?

[Warren P. <war...@gm...>]

Marius,

I respectfully disagree that the DUnit/X GUI is in the works. I have talked
over on the Google+ group to the people, and everyone is still in the navel
gazing stages.

Also, I disagree that the "Easy compatibility" feature is worthwhile. It's
not.  For my codebase, which has hundreds of unit tests apps, the rewrite
effort is far too large, for zero benefits to me.

I'm currently looking at DUnit2 and I think that a revived DUnit project
with the DUnit2 codebase looks far more promising to me than DUnit/X.

Warren


On Fri, Jan 9, 2015 at 4:54 AM, Marius Popescu <map...@gm...> wrote:

> Hi,
>
> While DUnitX is different than DUnit (in ways I appreciate), let me add
> that they provide an easy way to upgrade from DUnit.
> They have a unit called DUnitX.DUnitCompatibility that adds the CheckTrue
> etc methods used by DUnit and implements them over DUnitX.
>
> See the introduction here
> https://www.finalbuilder.com/resources/blogs/postid/697/introducing-dunitx,
> specifically:
>
> *Can I convert my DUnit Tests to DUnitX?*
>> DUnitX has limited support for DUnit Tests. Conversion to DUnitX is
>> relatively simple, DUnitX.DUnitCompatibility.pas has a TTestCase class with
>> all the Check(X) methods on it (marked as deprecated, which delegate to the
>> new Assert methods. In the uses clause, replace
>>
>> *TestFramework*with
>>
>> *DUnitX.TestFramework,DUnitX.DUnitCompatibility;*and change the
>> registration to
>> *TDUnitX.RegisterTestFixture(TYourTestClass)*
>
>
> Moreover, a GUI is in the works. The recent add of Command line parameters
> to run specific tests replaced a lot the need for a GUI.
>
> Kind regards,
> Marius Popescu
>
> On Fri, Jan 9, 2015 at 1:23 AM, Warren Postma <war...@gm...>
> wrote:
>
>> Juancarlo - I agree with you.
>>
>> I feel that DUnit/X is a real break with DUnit and offers nothing in the
>> way of even portability aids. It has no gui test runner. It is primitive, a
>> step backwards, for me.
>>
>> Why didn't DUnit2 get merged with DUnit?   That's what I want to know!
>>
>> Jeroen, are you still active on this mailing list?
>>
>> Warren
>>
>>
>> On Thu, Jan 8, 2015 at 7:20 PM, Juancarlo Añez <ap...@gm...> wrote:
>>
>>>
>>> On Thu, Jan 8, 2015 at 2:21 PM, Warren Postma <war...@gm...>
>>> wrote:
>>>
>>>> It's January 2015, and I haven't seen a significant change or any
>>>> interest in further development in dUnit since 2007.
>>>
>>>
>>> FWIW, I'm the original author, and I'm still listening, but I no longer
>>> use Delphi, so I have little to nothing to contribute to DUnit's evolution.
>>>
>>> I like what was done with DUnitX, and Dunit2. I don't understand why
>>> DunitX didn't try to bring in the Dunit community.
>>>
>>> Cheers,
>>>
>>> --
>>> Juancarlo *Añez*
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming! The Go Parallel Website,
>>> sponsored by Intel and developed in partnership with Slashdot Media, is
>>> your
>>> hub for all things parallel software development, from weekly thought
>>> leadership blogs to news, videos, case studies, tutorials and more. Take
>>> a
>>> look and join the conversation now. http://goparallel.sourceforge.net
>>> _______________________________________________
>>> Dunit-interest mailing list
>>> Dun...@li...
>>> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming! The Go Parallel Website,
>> sponsored by Intel and developed in partnership with Slashdot Media, is
>> your
>> hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>> look and join the conversation now. http://goparallel.sourceforge.net
>> _______________________________________________
>> Dunit-interest mailing list
>> Dun...@li...
>> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>>
>>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Dunit-interest mailing list
> Dun...@li...
> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>
>

Re: [DUnit-interest] Is DUnit dead?

[Juancarlo A. <ap...@gm...>]

On Fri, Jan 9, 2015 at 5:42 AM, Eoin Prout <eoi...@gm...> wrote:

> Juancarlo - Just want to say thanks for your work on DUnit, I use it
> everyday and really depend on it :)
>

Let's extend those thanks to all the contributors.

A lot of work was done after my initial version, and I did only a little
part of it.

Cheers,
-- 
Juancarlo *Añez*

Re: [DUnit-interest] Is DUnit dead?

[Kristofer S. [SSBV] <K....@ss...>]

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

Re: [DUnit-interest] Is DUnit dead?

[Eoin P. <eoi...@gm...>]

Juancarlo - Just want to say thanks for your work on DUnit, I use it
everyday and really depend on it :)

On Fri, Jan 9, 2015 at 12:20 AM, Juancarlo Añez <ap...@gm...> wrote:

>
> On Thu, Jan 8, 2015 at 2:21 PM, Warren Postma <war...@gm...>
> wrote:
>
>> It's January 2015, and I haven't seen a significant change or any
>> interest in further development in dUnit since 2007.
>
>
> FWIW, I'm the original author, and I'm still listening, but I no longer
> use Delphi, so I have little to nothing to contribute to DUnit's evolution.
>
> I like what was done with DUnitX, and Dunit2. I don't understand why
> DunitX didn't try to bring in the Dunit community.
>
> Cheers,
>
> --
> Juancarlo *Añez*
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Dunit-interest mailing list
> Dun...@li...
> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>
>

Re: [DUnit-interest] Is DUnit dead?

[Marius P. <map...@gm...>]

Hi,

While DUnitX is different than DUnit (in ways I appreciate), let me add
that they provide an easy way to upgrade from DUnit.
They have a unit called DUnitX.DUnitCompatibility that adds the CheckTrue
etc methods used by DUnit and implements them over DUnitX.

See the introduction here
https://www.finalbuilder.com/resources/blogs/postid/697/introducing-dunitx,
specifically:

*Can I convert my DUnit Tests to DUnitX?*
> DUnitX has limited support for DUnit Tests. Conversion to DUnitX is
> relatively simple, DUnitX.DUnitCompatibility.pas has a TTestCase class with
> all the Check(X) methods on it (marked as deprecated, which delegate to the
> new Assert methods. In the uses clause, replace
>
> *TestFramework*with
>
> *DUnitX.TestFramework,DUnitX.DUnitCompatibility;*and change the
> registration to
> *TDUnitX.RegisterTestFixture(TYourTestClass)*


Moreover, a GUI is in the works. The recent add of Command line parameters
to run specific tests replaced a lot the need for a GUI.

Kind regards,
Marius Popescu

On Fri, Jan 9, 2015 at 1:23 AM, Warren Postma <war...@gm...>
wrote:

> Juancarlo - I agree with you.
>
> I feel that DUnit/X is a real break with DUnit and offers nothing in the
> way of even portability aids. It has no gui test runner. It is primitive, a
> step backwards, for me.
>
> Why didn't DUnit2 get merged with DUnit?   That's what I want to know!
>
> Jeroen, are you still active on this mailing list?
>
> Warren
>
>
> On Thu, Jan 8, 2015 at 7:20 PM, Juancarlo Añez <ap...@gm...> wrote:
>
>>
>> On Thu, Jan 8, 2015 at 2:21 PM, Warren Postma <war...@gm...>
>> wrote:
>>
>>> It's January 2015, and I haven't seen a significant change or any
>>> interest in further development in dUnit since 2007.
>>
>>
>> FWIW, I'm the original author, and I'm still listening, but I no longer
>> use Delphi, so I have little to nothing to contribute to DUnit's evolution.
>>
>> I like what was done with DUnitX, and Dunit2. I don't understand why
>> DunitX didn't try to bring in the Dunit community.
>>
>> Cheers,
>>
>> --
>> Juancarlo *Añez*
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming! The Go Parallel Website,
>> sponsored by Intel and developed in partnership with Slashdot Media, is
>> your
>> hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>> look and join the conversation now. http://goparallel.sourceforge.net
>> _______________________________________________
>> Dunit-interest mailing list
>> Dun...@li...
>> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>>
>>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Dunit-interest mailing list
> Dun...@li...
> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>
>

Re: [DUnit-interest] Is DUnit dead?

[Warren P. <war...@gm...>]

Juancarlo - I agree with you.

I feel that DUnit/X is a real break with DUnit and offers nothing in the
way of even portability aids. It has no gui test runner. It is primitive, a
step backwards, for me.

Why didn't DUnit2 get merged with DUnit?   That's what I want to know!

Jeroen, are you still active on this mailing list?

Warren


On Thu, Jan 8, 2015 at 7:20 PM, Juancarlo Añez <ap...@gm...> wrote:

>
> On Thu, Jan 8, 2015 at 2:21 PM, Warren Postma <war...@gm...>
> wrote:
>
>> It's January 2015, and I haven't seen a significant change or any
>> interest in further development in dUnit since 2007.
>
>
> FWIW, I'm the original author, and I'm still listening, but I no longer
> use Delphi, so I have little to nothing to contribute to DUnit's evolution.
>
> I like what was done with DUnitX, and Dunit2. I don't understand why
> DunitX didn't try to bring in the Dunit community.
>
> Cheers,
>
> --
> Juancarlo *Añez*
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Dunit-interest mailing list
> Dun...@li...
> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>
>

Re: [DUnit-interest] Is DUnit dead?

[Juancarlo A. <ap...@gm...>]

On Thu, Jan 8, 2015 at 2:21 PM, Warren Postma <war...@gm...>
wrote:

> It's January 2015, and I haven't seen a significant change or any interest
> in further development in dUnit since 2007.


FWIW, I'm the original author, and I'm still listening, but I no longer use
Delphi, so I have little to nothing to contribute to DUnit's evolution.

I like what was done with DUnitX, and Dunit2. I don't understand why DunitX
didn't try to bring in the Dunit community.

Cheers,

-- 
Juancarlo *Añez*

Re: [DUnit-interest] Is DUnit dead?

[Paul S. <pv...@gm...>]

Hi Warren,

dUnitX looks like the future of unit-testing in Delphi.

If you [ca|wo]n't take the hit to migrate your tests and learn the new
framework, there is another aternative that is compatible with your
existing DUnit tests - DUnit2.

DUnit2 (http://sourceforge.net/projects/dunit2/) has several of the
features you describe and then some.

>From your feature wish-list:
* search for tests in the GUI runner form
* double-clicking on a failing test in the GUI runner opens the
corresponding test unit in the Delphi IDE, positioned at the failing line
in the source code. Enable this feature by compiling and installing the
DUnitTestInspector package for your Delphi version (
http://sourceforge.net/p/dunit2/code/HEAD/tree/trunk/projects/)

Also:
* greatly extended GUI testing support, including automated script
recording.
* wizards for creating test projects and test class templates.
* a visual breadcrumb trail for the current test - a useful aid to track
the the progress of the test runner if you have a large, nested and
long-running test suite.

Cheers, Paul.

On Fri, Jan 9, 2015 at 5:51 AM, Warren Postma <war...@gm...>
wrote:

> It's January 2015, and I haven't seen a significant change or any interest
> in further development in dUnit since 2007.
>
> In my opinion, the GUI test runner is the main reason I'm still using it,
> instead of dUnitX.
>
> I think that DUnit should be continued, and improved.  I have a few local
> improvements added to my own private version, that I'd like to contribute,
> and I'm wondering if I should start a fork, or continue development using
> SVN on sourceforge?
>
> Is anyone interested in starting a fork of DUnit?   In my opinion, the
> sourceforge site, the svn repo, etc, are basically moribund.
>
> A modern way to continue DUnit development would be on Bitbucket or
> Github, and move to Mercurial (bitbucket) or Git.
>
> I have added a way to search for a test by name (very useful in large
> collections of tests), and it saves you from looking up and down a list for
> a particular test.
>
> I'm thinking that the gui test runner really needs to be better integrated
> with the IDE.  I should be able to go from a unit that is open in the IDE
> (I have  MyTest.pas open in the editor), to selecting and running just that
> test, in a  large test app.  So for example, if the IDE has ONE open editor
> tab, that tab's class name should be shared with the running GUI test
> runner, letting you focus on that test, so that you can run just that one
> test.  Secondly, when a test fails, double clicking it should (if the IDE
> was open), open that unit in the IDE and move to that line of code.
>
> IDES like Eclipse, and Netbeans, and Visual studio have had all this for
> ten years.
>
> Warren Postma
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Dunit-interest mailing list
> Dun...@li...
> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>
>

[DUnit-interest] Is DUnit dead?

[Warren P. <war...@gm...>]

It's January 2015, and I haven't seen a significant change or any interest
in further development in dUnit since 2007.

In my opinion, the GUI test runner is the main reason I'm still using it,
instead of dUnitX.

I think that DUnit should be continued, and improved.  I have a few local
improvements added to my own private version, that I'd like to contribute,
and I'm wondering if I should start a fork, or continue development using
SVN on sourceforge?

Is anyone interested in starting a fork of DUnit?   In my opinion, the
sourceforge site, the svn repo, etc, are basically moribund.

A modern way to continue DUnit development would be on Bitbucket or Github,
and move to Mercurial (bitbucket) or Git.

I have added a way to search for a test by name (very useful in large
collections of tests), and it saves you from looking up and down a list for
a particular test.

I'm thinking that the gui test runner really needs to be better integrated
with the IDE.  I should be able to go from a unit that is open in the IDE
(I have  MyTest.pas open in the editor), to selecting and running just that
test, in a  large test app.  So for example, if the IDE has ONE open editor
tab, that tab's class name should be shared with the running GUI test
runner, letting you focus on that test, so that you can run just that one
test.  Secondly, when a test fails, double clicking it should (if the IDE
was open), open that unit in the IDE and move to that line of code.

IDES like Eclipse, and Netbeans, and Visual studio have had all this for
ten years.

Warren Postma

[DUnit-interest] TimeSeparator with new Delphi

[Borneq <bo...@wp...>]

In GUITestRunner.pas should be :
   {$IF RTLVersion>=24.00}FormatSettings.{$ifend}TimeSeparator := ':';
instead
   TimeSeparator := ':';

[DUnit-interest] Asserting the content of complex data structures

[Alain D. <ala...@gm...>]

Just starting to use DUnit, and wondering if there are assertions for
comparing complex data structures. For example, comparing the content of
one array to that of another array?

I tried CheckEquals() passing it two arrays, but it doesn't compile. I
googled around for something like Assert.AreEqual() (as in C#), but haven't
found anything for Delphi.

Cheers,


*Alain Désilets*
Owner, Alpaca Technologies
ala...@gm...
alpacatechnologies.com

Re: [DUnit-interest] DUnitX

[Fernando M. <fgm...@gm...>]

Looks really nice! Keep up the good work!

Best regards,
Fernando Macedo

"Somos o que repetidamente fazemos; a excelência, portanto, não é um feito,
mas sim um hábito!" - Aristóteles


On Mon, Sep 23, 2013 at 11:58 AM, Juancarlo Añez
<jua...@gm...>wrote:

> Hello,
>
> Many should be interested in a completely new generation of unit testing
> in Delphi:
>
>
> http://www.finalbuilder.com/Resources/Blogs/PostId/697/introducing-dunitx.aspx
>
> Cheers,
>
> --
> Juancarlo *Añez*
> tel:+58(414)901-2021
> skype:juancarloanez
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
> _______________________________________________
> Dunit-interest mailing list
> Dun...@li...
> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>
>

[DUnit-interest] DUnitX

[Juancarlo A. <jua...@gm...>]

Hello,

Many should be interested in a completely new generation of unit testing in
Delphi:

http://www.finalbuilder.com/Resources/Blogs/PostId/697/introducing-dunitx.aspx

Cheers,

-- 
Juancarlo *Añez*
tel:+58(414)901-2021
skype:juancarloanez

Re: [DUnit-interest] DUnit XE-XE2

[Paul S. <pv...@gm...>]

Hi Dmitry,

Apologies for the delay. Thankyou for your kind words.
I haven't been actively involved with either DUnit or DUnit2 for several
years.

I stopped developing and supporting the DUnit wizard I wrote since the
developers of Delphi added their own wizard to the Delphi IDE.
Your efforts may be better directed at improving the built-in wizard.
However, a cautionary note: I did offer my code and help when I heard a
built-in DUnit wizard was planned for Delphi, but my emails to Borland
developers were ignored.

If you wish to further developer the wizard in the DUnitX codebase we  need
to clarify a couple of things.

1) Do you want to commit your changes to DUnit or DUnit2?
    The two projects are largely API-compatible, but the implementations
differ. There are some new features in the DUnit2 interface.
    There have been a couple of efforts to merge the two codebases, but as
I recall, there were some issues with DUnit2 and the Abbrevia open source
products

2)  The DUnit/DUnit2 codebase is licenced under the GPL Open Source
licence. You cannot add the copyright notice you have proposed: "Copyright
(c) 2013 by Soft 4 POS http://www.soft4pos.com", as that would be a breech
of the GPL licences. All contributions to the codebase must preserve the
original licence.

Cheers, Paul.







On Sun, Jun 16, 2013 at 4:03 PM, di...@st... <di...@st...>wrote:

> **
>  Dear friends,
>
>  I'm going to make submission of DUnit IDE wizard for Delphi XE-XE2,
>  which is port of existing D7 source codes with fixing Unicode issues.
>  I can not reach the Paul Spain the latest author of Wizard source codes.
> It's my respects to that person!
>
>  So my question is. To abide OpenSource policy and previous authors
> rights, I need to provide the preambule section for
>  files in source codes which includes authors copyrights and etc.
>
>  Hopefully I'm going to support and extend the Wizard functionality for
> future versions.
>  I believe that my knowledge of OTapi and the rest delphi staff is rather
> limited compared with
>  yours guys(mentioned in DUnit project), so I will be happy to be managed
> and collaborate
>  on the project development issues.
>
>  can you please prepare for me such preambule or to give some directions
> on that.
>
>  The preambule I have now is, please let me know if something wrong.
>  //////////////////////////////////////////////////////////////////////////////////////////////////
>
>     Original authors
>
> * Kent Beck <ken...@cs...>
> * Erich Gamma <Eri...@ot...>
> * Juanco Aсez <ju...@us...>
> * Paul Spain <pa...@xp...>
>
> contributors
> * Dmitry Konnov <kon...@ma...>
>
> Contact Dmitry Konnov via email: kon...@ma...
> Copyright (c) 2013 by Soft 4 POS http://www.soft4pos.com
>  //////////////////////////////////////////////////////////////////////////////////////////////////
>
>
>
>  Thank you
>  Dmitry Konnov
>    <http://www.soft4pos.com/>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Dunit-interest mailing list
> Dun...@li...
> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>
>

Re: [DUnit-interest] DUnit XE-XE2

[Peter H. <pet...@gm...>]

Hi Dimitry,

I have forwarded your email to Paul.

P.
On 16/06/2013 4:03 PM, "di...@st..." <di...@st...> wrote:

> **
>  Dear friends,
>
>  I'm going to make submission of DUnit IDE wizard for Delphi XE-XE2,
>  which is port of existing D7 source codes with fixing Unicode issues.
>  I can not reach the Paul Spain the latest author of Wizard source codes.
> It's my respects to that person!
>
>  So my question is. To abide OpenSource policy and previous authors
> rights, I need to provide the preambule section for
>  files in source codes which includes authors copyrights and etc.
>
>  Hopefully I'm going to support and extend the Wizard functionality for
> future versions.
>  I believe that my knowledge of OTapi and the rest delphi staff is rather
> limited compared with
>  yours guys(mentioned in DUnit project), so I will be happy to be managed
> and collaborate
>  on the project development issues.
>
>  can you please prepare for me such preambule or to give some directions
> on that.
>
>  The preambule I have now is, please let me know if something wrong.
>  //////////////////////////////////////////////////////////////////////////////////////////////////
>
>     Original authors
>
> * Kent Beck <ken...@cs...>
> * Erich Gamma <Eri...@ot...>
> * Juanco Aсez <ju...@us...>
> * Paul Spain <pa...@xp...>
>
> contributors
> * Dmitry Konnov <kon...@ma...>
>
> Contact Dmitry Konnov via email: kon...@ma...
> Copyright (c) 2013 by Soft 4 POS http://www.soft4pos.com
>  //////////////////////////////////////////////////////////////////////////////////////////////////
>
>
>
>  Thank you
>  Dmitry Konnov
>    <http://www.soft4pos.com/>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Dunit-interest mailing list
> Dun...@li...
> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>
>

[DUnit-interest] DUnit XE-XE2

[<di...@st...>]

Dear friends,

I'm going to make submission of DUnit IDE wizard for Delphi XE-XE2,
which is port of existing D7 source codes with fixing Unicode issues.
I can not reach the Paul Spain the latest author of Wizard source codes. It's my
respects to that person!

So my question is. To abide OpenSource policy and previous authors rights, I
need to provide the preambule section for
files in source codes which includes authors copyrights and etc.

Hopefully I'm going to support and extend the Wizard functionality for future
versions.
I believe that my knowledge of OTapi and the rest delphi staff is rather limited
compared with
yours guys(mentioned in DUnit project), so I will be happy to be managed and
collaborate
on the project development issues.

can you please prepare for me such preambule or to give some directions on that.

The preambule I have now is, please let me know if something wrong.
//////////////////////////////////////////////////////////////////////////////////////////////////
   Original authors

* Kent Beck <ken...@cs...>
* Erich Gamma <Eri...@ot...>
* Juanco Aсez <ju...@us...>
* Paul Spain <pa...@xp...>

contributors
* Dmitry Konnov <kon...@ma...>

Contact Dmitry Konnov via email: kon...@ma...
Copyright (c) 2013 by Soft 4 POS http://www.soft4pos.com

//////////////////////////////////////////////////////////////////////////////////////////////////


Thank you
Dmitry Konnov
  <http://www.soft4pos.com/>

Re: [DUnit-interest] test

[Juancarlo A. <ap...@gm...>]

Dimitry,

It seems you're in.

Friends, Dimitry wants to contribute, and needs guidance.

Thanks in advance,


On Sun, Jun 16, 2013 at 12:22 AM, di...@st... <di...@st...>wrote:

> **
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Dunit-interest mailing list
> Dun...@li...
> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>
>


-- 
Juancarlo *Añez*

[DUnit-interest] Questions about DUnit

[Felipe M. M. <fel...@gm...>]

Hi!

I'm a Delphi 7 developer from Brazil, and our development team is very
interested to use DUnit for TDD into our projects.  We've runned few
assertive tests and we want to use DUnit as our official unit tests tool. I
got in touch with Juancarlo Añez and he sent me this email address. So, if
you could gently help us, we need to make some few questions about DUnit.

1) What if we need support (for developers only)? Do you have and specific
forum, or we can try to reach you by email? We're new to DUnit, so, if we
need some assistance or any kind of help, where should we go?

2) Is there any bug tracking tool where I cand post bugs (if they appear)?


Sincerely,

Felipe Marin Mota

Re: [DUnit-interest] DUnit improvements

[Mark E. <med...@us...>]

Hi Kris,

We were still running CLR tests internally, but we disabled those back 
when we shipped XE2. I don't expect the framework code it would ever be 
used again. If it needs to be resurrected in the future it can be 
extracted from an older version of DUnit as needed.

I was under the impression that the stack track information came from 
JCL, but to be honest I haven't looked at it too closely.

Mark

On 10/3/2012 10:20 AM, Kris Golko wrote:
> Hi Mark,
>
> Delphi.Net is dicontinued, should we remove CLR code or is=
> there a chance for it to be reused in WinRT (with some modifications)?
>
> I hoped we will be able to get the stack trace from the StackTrace prope=
> rty. Apparently it's not that simple
>
> ------------------------------------------------------------------------
> *From:* Mark Edington <med...@us...>
> *To:* Users of the DUnit Xtreme testing framework for Delphi 
> <dun...@li...>
> *Sent:* Monday, 1 October 2012, 21:39
> *Subject:* Re: [DUnit-interest] DUnit improvements
>
> Kris,
>
> I'm all for making incremental improvements to the framework, and this 
> certainly seems like something that would be very useful to have. With 
> the current RTTI support, it should even be possible to avoid having 
> to explicitly call RegisterTest for each test class.
>
> This does bring up again the whole DUnit2 discussion, and if it makes 
> sense to embrace invest this older code base or the newer one.
>
> -- Mark
>
> On 9/30/2012 12:23 PM, Juancarlo Añez wrote:
>> Kris,
>>
>> It makes sense.
>>
>> As long as there's a Delphi 7 compatible version, most projects will 
>> be fine.
>>
>> -- Juanca
>>
>> On Sun, Sep 30, 2012 at 3:59 AM, Kris Golko <krz...@ya... 
>> <mailto:krz...@ya...>> wrote:
>>
>>     Hi All,
>>
>>     As Delphi supports attributes now, it would be easy to modify
>>     DUnit, so a test procedure is designates as test by applying
>>     the [test] attribute (mirroring NUnit). While trying to implement
>>     the change I realised that further modifications are needed - you
>>     can only find pointer to a procedure if it's published, so the
>>     procedure needs to be executed using TRttiMethod.Invoke. I have a
>>     prototype working, but I can't help noticing that the code is
>>     becoming increasingly cluttered and suboptimal. For example,
>>     TMethodEnumerator could be eliminated.
>>
>>     Currently DUnit design reflects limitation of earlier versions of
>>     Delphi. As these limitation have been overcome in Delphi 2010, I
>>     think the best course of action would branching DUnit to create
>>     DUnit for Delphi 2010 and above. It would allow to rationalise
>>     the code and open the way to further improvements.
>>
>>     What do you reckon?
>>
>>
>>
>>
>>     ------------------------------------------------------------------------------
>>     Everyone hates slow websites. So do we.
>>     Make your web apps faster with AppDynamics
>>     Download AppDynamics Lite for free today:
>>     http://ad.doubleclick.net/clk;258768047;13503038;j?
>>     http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>>     _______________________________________________
>>     Dunit-interest mailing list
>>     Dun...@li...
>>     <mailto:Dun...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/dunit-interest
>>
>>
>>
>>
>> -- 
>> Juancarlo *Añez*
>
>
> ------------------------------------------------------------------------------
> Got visibility?
> Most devs has no idea what their production app looks like.
> Find out how fast your code is with AppDynamics Lite.
> http://ad.doubleclick.net/clk;262219671;13503038;y?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> _______________________________________________
> Dunit-interest mailing list
> Dun...@li... 
> <mailto:Dun...@li...>
> https://lists.sourceforge.net/lists/listinfo/dunit-interest
>
>