-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update testing directions #534
Comments
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. |
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. |
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:
***@***.***>
|
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.
The text was updated successfully, but these errors were encountered: