Asserting in __TRY __CATCH

[ZigaJavornik]

TcUnit version 1.3.1.
TwinCAT version 4026.26

I was wondering if anyone has tried doing assertions in TwinCAT 4026 in the __TRY__CATCH statement. The test assertion works (I think) to a point where the fail is reported but the message is not written to the output window.

Example:

IF TcUnit.TEST_ORDERED(__POUNAME()) THEN

	__TRY
		// Do your assertions here...
		AssertEquals_LREAL(
			Expected := 50,
			Actual :=  F_ConvertEncoderPositionToMilimeters(0, 0),
			Delta := 0.001,
			Message := 'Implement tests!');
	__CATCH(e)
			AssertFalse(
				Condition := TRUE, 
				Message := Tc2_Standard.CONCAT('Failed converting position when 0 is provided to position and counts. Exception: ', TO_STRING(e)));
	__ENDTRY
	
	TcUnit.TEST_FINISHED();
END_IF

The function will intentionaly fail before implementation due to division with 0. To check for this the try catch is used. I have 3 tests in total, and 1 has failed while 2 have passed, though there is no message reported:

[ZigaJavornik]

As I clicked post I figured it out....

The problem is that Tc2_Standard.CONCAT returns an empty string - this is most likely due to the _SYSTEM.ExceptionCode not having {attribute 'to_string'} or maybe it is behaving differently because the type is located in the __SYSTEM namespace (which does not have intellisense, maybe it is all connected, who knows).

[ZigaJavornik]

Actually the problem is probably due to a too long of a text to be written to the output window, see below examples, where I was trying to trim the string and got it to be dsplayed when I cut out 10 characters. I know that when I was running tests on TwinCAT4024, when the message was too long, it would just say that in the output window, but now there is nothing displayed - this is probably TwinCAT/XAE shell (64 bit) issue with how ADSLOGSTR is working in the 4026 build? Let me know if this should be considered a bug and maybe have a warning displayed somewhere when the text is too long?