Feature(runner): capture output

[ynfle]

Supersedes #26 (my mess up because I deleted my fork before this was merged) Closes #13

• Feature(unittest_json): add messages when tests start and finish
• Feature(runner): capture output
• Fix(runner): use native JsonNode instead of the type
• Test(runner): test capturing stdout & stderr and writing to json
• Fix(runner): include trailing whitespace from output
• Fix(runner): truncate user output for unicode lenght of 500 with message
• Test(runner): test for truncation message and unicode length
• Fix: Fix typo in directory name
• Test: Remove fail/multiple_tests_one_fail output cases
• Test: Remove fail/multiple_tests_all_fail output case
• Test: Use proc instead of func and debugEcho
• Test: Improve pass/single_test_output case
• Test: Improve pass/multiple_tests_output_truncated
• Test: Improve pass/multiple_tests_output_unicode_truncated
• Refactor: Nitpick style
• Refactor(runner): Simplify result assignment from execCmdEx
• Refactor(unittest_json): Remove export markers again
• Fix(runner): Fix return type in run proc doc comment
• Refactor(runner): Change a misleading let to a var
• Fix(runner): Don't truncate output that has rune-length of 500
• Test: Improve pass/single_test_output_unicode
• Test: Add pass/single_test_output_stderr_only

[iHiD]

Thank you for this! 💙

@ee7 is knee-deep in Conflgiet atm (which I imagine is going to take their time up till launch) so I suggest that if you're broadly happy with this, we just get it merged down and then any improvements can be made later, rather than get too caught up in review cycles at this stage. I've therefore tagged @ErikSchierboom who can maybe give it a quick sanity check for you for now! :)

[ynfle]

@ee7 Had a requested a bunch of stuff that was requested and PRed on my branch (which I, unthoughtfully, deleted without waiting until this PR was merged) which can always be addressed later. @ee7, what do you think?

[ee7]

we just get it merged down and then any improvements can be made later, rather than get too caught up in review cycles at this stage

The main part of the review is done. I just need to do a couple of things to fix this PR. Don't merge this yet.

I think I'll be able to merge this within the next 24 hours.

[ynfle]

we just get it merged down and then any improvements can be made later, rather than get too caught up in review cycles at this stage

The main part of the review is done. I just need to do a couple of things to fix this PR. Don't merge this yet.

I think I'll be able to merge this within the next 24 hours.

I rebased on main. What were you planning on fixing?

[ee7]

. What were you planning on fixing?

First I'll make CI green again - it's currently failing on this PR.

See https://github.com/exercism/nim-test-runner/pull/49.

Then I'll make it so the new test cases actually run. Currently they're silently skipped - scroll down here and notice that, although the check is green, no output capture tests actually ran.

[ee7]

Ping @iHiD - can you review this one too?

I'm setting this back to draft because I see:

Merging can be performed automatically with 1 approving review.

But I don't want automatic merging here - I want to merge this myself. And GitHub's automatic merging is new enough that I don't understand its subtleties.