Update testing directions

[BNAndras]

Using Delphi 12, my solution compiles for me and spits out an XML file with the DUnitX results. It seems I could document the location and structure of this file inside our testing directions. I'd provide an example test suite and results so students know how to interpret the results.

[rpottsoh]

I don't know how useful this. I also don't know that it isn't useful at all as well. The onscreen output is typically enough to help the programmer figure out what needs to be fixed. The test result should be providing expected result when a test fails. I don't want to discourage you from helping out in anyway possible. Just pointing out how I see things.

[BNAndras]

The thing is I’m not seeing any onscreen output. Using the Delphi 12 defaults and the bundled DXUnit, the compiled program flashes and then closes on Windows 11. Therefore, I need to check the results XML file.

[rpottsoh]

Run the object code in a cmd prompt and not from the debugger.

…

On Fri, Jan 10, 2025, 10:03 AM András B Nagy ***@***.***> wrote: The thing is I’m not seeing any onscreen output. Using the Delphi 12 defaults and the bundled DXUnit, the compiled program flashes and then closes on Windows 11. Therefore, I need to check the results XML file. — Reply to this email directly, view it on GitHub <#534 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVHTUZYH4BVXQDSCVQ5MOD2J7OMXAVCNFSM6AAAAABU5OVXV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBSHEYTAMZWGE> . You are receiving this because you commented.Message ID: ***@***.***>

[BNAndras]

You mean run the compiled executable? The console window opens, runs, and closes. The DUnitX XML file is updated correctly with all tests passing.

[rpottsoh]

@BNAndras that is correct. If you open a command prompt at the location of the exe, when you run it, you will see the results of the test on the screen. You miss this when you run the testrunner from the debugger because the execution window is immediately closed. If you set TDUnitx.Options.ExitBehavior equal to TDUnitXExitBehavior.Pause then execution will be paused at the very via. a readln statement, see the .DPR of any of the exercises. I am not sure the best way to set the ExitBehavior, maybe there is a command line parameter you can have Delphi pass, short of that you could just force the readln to occur. Personally, I just run the exe from the command line unless I need to use the debugger.