New LDATE/LTIME types are not supported.

[TheColonel2688]

FB_TestSuite.AssertEquals_LDATE does not exist

There is no built in way to assert an LDATE

LDATE
LDATE_AND_TIME
LTIME_OF_DAY
are not supported.

[ZigaJavornik]

You can always use AssertEquals() which will compare any data types. Only downside is, the printed error won't be in the provided format and the assertion can't be made with non-variable types (direct comparison with literals).

[sagatowski]

Also, the LDATE/LDATE types are not supported by TwinCAT < 4026.0. As it stands now, most are still on < 4026.0, so upgrading TcUnit to a compiler that only supports 4026.0 or later isn't a great idea.
Support for this will be added when the whole TcUnit toolchain is upgraded to use VS2022 and 4026 only.

[TheColonel2688]

That's fair, I'm using CoUnit, and 64 bit date and time types have been in the codesys compiler for quite a while.

[sagatowski]

Moving this to TcUnit 2.0 as to not break compatibility with <= 4024.x.

[rschluep-posalux]

Hello,

[EDIT] LTIME is already supported. This trick is meant to work for the other missing types like LDATE LDATE_AND_TIME LTIME_OF_DAY.

Using this page: Conditional pragmas

I have found that this is possible:

METHOD PUBLIC AssertEquals_LTIME : BOOL
VAR_INPUT
    {IF defined (type: __SYSTEM.TYPE_CLASS.TYPE_LTIME)}
        Expected : LTIME;       // LTIME expected value
        Actual   : LTIME;       // LTIME actual value
        Message  : T_MaxString; // The identifying message for the assertion error
    {ELSE} // Completely optionnal
        Expected : TIME;        // Completely optionnal
        Actual   : TIME;        // Completely optionnal
        Message  : T_MaxString; // Completely optionnal
    {END_IF}
END_VAR
VAR
    TestInstancePath : T_MaxString;
    AlreadyReported  : BOOL;
END_VAR
===
{IF NOT (hastype (variable: Expected, LTIME))}
    // Add incompatibility message here. The compiler will build the method regardless of its usage.
    // So the only way I found for now is to let it compile and inform the user during the runtime.
    // Since it is a Unit test framework, I think a simple assertion here is enough :)
{ELSE}
    // add code here
{END_IF}

I have tested this behavior with the 4026.15 and the 4024.75 build version, both have the exected behavior :)