I know I'm late to the party here, but can anyone tell me why, in DUnit, they changed the XML output format in XMLTestRunner.pas?

-
I know I'm late to the party here, but can anyone tell me why, in DUnit, they changed the XML output format in XMLTestRunner.pas?

I discovered this change as part of the move from XE to DX Seattle.

Comments

  1. Uwe SchusterOctober 23, 2015 at 8:54 AM

    Because it is DUnitX instead of DUnit since XE8?

    http://docwiki.embarcadero.com/RADStudio/XE8/en/What's_New_in_Delphi_and_C%2B%2BBuilder_XE8#Testing_Framework_Changes_for_XE8

    ReplyDelete
  2. Asbjørn HeidOctober 23, 2015 at 9:57 AM

    Uwe Schuster That just says DunitX is supported, not that they switched to it. Poor wording?

    ReplyDelete
  3. Stefan GlienkeOctober 23, 2015 at 9:59 AM

    Uwe Schuster Nope, DUnitX is just additional. DUnit still is shipped.

    They didn't change anything. You probably used the modified XMLTestRunner unit by VSoft  that is Continua/NUnit compatible in one of these two Delphi versions. Delphi ships with the stoneage version of that file ($BDS)\source\DUnit\Contrib\XMLReporting

    ReplyDelete
  4. Jeroen Wiert PluimersOctober 23, 2015 at 12:59 PM

    The old DUnit XMLTestRunner concatenates XML using strings. The VSoft one using XmlDocument but doesn't support everything DUnit does. The FinalBuilder one also uses strings, but produces more NUnit compatible XML. So take your pick (:

    ReplyDelete
  5. Nick HodgesOctober 26, 2015 at 5:35 AM

    Well, I'm an idiot once again.  Turns out that DUnit hasn't changed, we did.  We put this in place:

    http://cc.embarcadero.com/Item/28239

    But didn't change the file name.  No wonder I thought it  had changed.

    ReplyDelete
  6. Asbjørn HeidOctober 26, 2015 at 5:37 AM

    Nick Hodges Assumptions strike again ;)

    ReplyDelete
  7. Jeroen Wiert PluimersOctober 26, 2015 at 3:04 PM

    Nick Hodges oh gosh, yet another test runner.

    ReplyDelete

Post a Comment