Division by zero when clicking on the "Discover Tests" button in TestInsight Explorer

[Lübbe Onken]

Testinsight 1.1.8.0

RAD Studio Sydney 27.0.37889.9797 plus the first patch applied via GetIt

TMS VCL UI Pack 10.3.2.0

The test cases are written in DUnitX, but the DUnit* are not installed with RAD Studio. We use an up to date version of DUnitX and include this one in the search path.

[165EC650]{TestInsight10Sydney.dll} Unbekannte Funktion bei __dbk_fcall_wrapper + $CAC90
[165C86A7]{TestInsight10Sydney.dll} Unbekannte Funktion bei __dbk_fcall_wrapper + $A6CE7
[50D6B1FD]{vcl270.bpl  } Vcl.ComCtrls.TProgressBar.GetMax (Line 13564, "Vcl.ComCtrls.pas" + 1) + $2
[165EC644]{TestInsight10Sydney.dll} Unbekannte Funktion bei __dbk_fcall_wrapper + $CAC84
[165ED81C]{TestInsight10Sydney.dll} Unbekannte Funktion bei __dbk_fcall_wrapper + $CBE5C
[165ED909]{TestInsight10Sydney.dll} Unbekannte Funktion bei __dbk_fcall_wrapper + $CBF49
[166265DD]{TestInsight10Sydney.dll} Unbekannte Funktion bei __dbk_fcall_wrapper + $104C1D
[165F20BC]{TestInsight10Sydney.dll} Unbekannte Funktion bei __dbk_fcall_wrapper + $D06FC
[5017D013]{rtl270.bpl  } System.Classes.CheckSynchronize (Line 15419, "System.Classes.pas" + 34) + $A
[0BAE0F4B]{fmx270.bpl  } FMX.Platform.Win.TPlatformWin.ThreadSync (Line 3289, "FMX.Platform.Win.pas" + 3) + $2
[50181184]{rtl270.bpl  } System.Classes.StdWndProc (Line 17989, "System.Classes.pas" + 8) + $0
[50EBF04F]{vcl270.bpl  } Vcl.AppEvnts.TMultiCaster.GetAppEvents (Line 657, "Vcl.AppEvnts.pas" + 1) + $B
[50E5A71F]{vcl270.bpl  } Vcl.Forms.TApplication.ProcessMessage (Line 11002, "Vcl.Forms.pas" + 23) + $1
[50E5A762]{vcl270.bpl  } Vcl.Forms.TApplication.HandleMessage (Line 11032, "Vcl.Forms.pas" + 1) + $4
[50E5AA95]{vcl270.bpl  } Vcl.Forms.TApplication.Run (Line 11170, "Vcl.Forms.pas" + 26) + $3
[0051E104]{bds.exe     } bds.bds (Line 222, "" + 13) + $2

The test are run when I click on the “Run all tests” button. Afterwards single tests can be selected and run via “Run selected tests”

[Stefan Glienke]

I see - it’s a glitch with counting skipped tests (which it does when running discover) on DUnitX (it reports 0 then) and an optimization (so I thought) for the progress bar.

[Stefan Glienke]

Attached the fixed file for DUnitX to properly count the tests even if they are skipped.

[Lübbe Onken]

I can confirm that the issue is fixed. Thanks a lot!
Did you already update the installer? If not, you might get more of these bugreports

[Daniel Trierweiler]

Hi! I just stumbled upon this issue as well and can also confirm the fix. Do you have any plans on updating the installer?

[Lucas Postingher]

Do you have any plans on updating the installer?

[Stefan Glienke]

fixed issue #135

→ <<cset c93c71a843fd>>