-
There is a discrepancy between of the output of TIME_TO_STRING between 4022 and 4024. This makes certain tests of the TcUnit-Verifier to fail.
For example, one expected output of a test would be:
FA…
-
Hi,
I was wondering why you have chosen CODESYS V2.3 for the implementation?
I mean, what are your specific reasons?
With kind regards,
Aliazzz
-
In the [`CONTRIBUTING.md`](https://github.com/tcunit/TcUnit/blob/master/CONTRIBUTING.md) you mention that we should use the same Visual Studio version number as the original solution file. I found tha…
-
Relating to: #37
I was trying to use tcunit to test a statechart, using a case statement. I acknowledge this is somewhat outside the normal realm of unit testing. Regardless, using a case statemen…
-
Hi there
I'd like to suggest a small 'upgrade' to replace the GVL_Constants_TcUnit with a parameter list.
The advantage of a parameter list is that the parameterlist is still part of the Libray wh…
-
I tried out the TEST_FINISHED_NAME function and found out that I completely misunderstood its meaning. I thought this function was meant to check if a certain test had finished or not. However, it _se…
-
Related to issue #38.
If TEST_FINISHED_NAMED is called with a name for a test that doesn't exist, the user should be warned (by standard ADSLOGSTR).
-
Hi!
For #11 it would be mutually beneficial to have all results in a single place.
number of succes,
number of failed,
number of test-suites
all test suites;
per test suite, all tests;
pe…
-
As discovered in issue #26, doing many ADSLOGSTR(), it seems that the AMS-router looses some of them. For instance, running the TcUnit-Verifier makes it report different results (in terms of how many …
-
If you have a project that is using TcUnit and that is using the TE1200 static code analysis tool from Beckhoff, it will issue an warning "SA0027: Object name 'GVL_Constants' already used in Library '…