Activity for co♻e: unittest framework for CODESYS

yptfindy posted a comment on ticket #65

2026-05-04T15:03:13.478000Z

Hi everyone, I’m running into the same memory issue, but I’m using a newer version of CODESYS where I can’t seem to find the “Library Parameters” section in the Library Manager anymore. From what I’ve read online, it looks like this feature might have been deprecated. Given that, what would be the recommended way now to limit things like the number of test suites? Is there an alternative configuration approach in newer CODESYS versions to reduce memory usage? Thanks in advance for your help!

sergeyglukhov posted a comment on ticket #54

2025-07-18T07:55:14.162000Z

any chance this could go to the github anytime soon?

bnewman modified a comment on ticket #71

2025-07-07T20:53:49.348000Z

Note: I should say they are marked INTERNAL, not PRIVATE

bnewman posted a comment on ticket #71

2025-07-07T20:48:08.926000Z

Note: I should say they are marked INTERNAL, not PROTECTED

bnewman created ticket #71

2025-07-07T20:45:45.296000Z

Test Suit Methods should be Protected not Private

bnewman created ticket #70

2025-07-07T19:57:45.678000Z

AssertEquals_String doesn't work for Strings longer than 255 characters

i-campbell modified a wiki page

2025-02-26T16:37:32.606000Z

Home

Ingo created ticket #69

2025-02-06T08:23:47.036000Z

Links to help.codesys.com are dead

eguerra posted a comment on ticket #65

2024-10-07T12:32:41.714000Z

Library Manager -> Library Parameters (near placeholders) There you can change parameters like the max number of test suites, the max number of tests per test suite or the max number of asserts per test

bnewman posted a comment on ticket #67

2024-09-04T21:03:24.876000Z

this can be closed BTW

bnewman posted a comment on ticket #67

2024-07-11T18:27:33.401000Z

I think this is the same or similar to https://forge.codesys.com/lib/counit/tickets/58/ I figured out that this was occurring because assert was being called continuously

eschwellinger posted a comment on ticket #59

2024-06-19T09:57:14.795000Z

For security reasons, we had to shut down the faq.codesys.com page. The content will gradually be integrated into the CODESYS Online Help System (https://www.helpme-codesys.com). Here the preliminary faq file for download.

bnewman posted a comment on ticket #59

2024-06-07T18:34:44.546000Z

Seems to work now. Can this be closed?

bnewman created ticket #68

2024-06-07T18:33:36.620000Z

Request: Tutorial for Jinkins and example Python Scripts

bnewman created ticket #67

2024-06-07T18:25:45.503000Z

AccessViolation Exception thrown in FB_AssertResultStatic.AddAssertResult()

azabala modified a comment on ticket #66

2024-05-09T06:21:23.899000Z

For anyone looking for a solution to a similar problem: * You should install a newer version of CodeSys (e.g. 3.5 SP19) * Open newer version of CodeSys * Import the project * Click File > Save Project as * Select the appropriate file type according to the target CodeSys version - in case of CodeSys 3.5 SP11 select Library files (CODESYS V3.5 SP11) (*.library) * Click Save Now you will be able to open the .library with the target CodeSys version.

azabala posted a comment on ticket #66

2024-05-08T13:39:25.955000Z

For anyone looking for a solution to a similar problem: * You should install a newer version of CodeSys (e.g. 3.5 SP19) * Open newer version of CodeSys * Import the project * Click File > Save Project as * Select the appropriate file type according to the target CodeSys version - in case of CodeSys 3.5 SP19 select Library files (CODESYS V3.5 SP11) (*.library) * Click Save Now you will be able to open the .library with the target CodeSys version.

azabala created ticket #66

2024-05-08T11:34:31.651000Z

CoUnit Library installation error in CodeSys 3.5 SP11

elpanoo1 posted a comment on ticket #65

2024-02-13T13:33:41.095000Z

Can you give me an example on how this should look like?

hermsen posted a comment on ticket #65

2024-02-12T17:29:05.516000Z

Hi, Yes it seems the program will not fit in your PLC memory. To resole this you can use the parameters in the CoUnit library to limit the various array sizes.

elpanoo1 created ticket #65

2024-02-12T07:32:42.731000Z

coUnitRunner Error: no more free global space

aguado posted a comment on ticket #64

2023-10-27T14:39:57.967000Z

Hi, this might help you: https://forge.codesys.com/tol/codesys-4-linux/docker/ci/master/tree/codesys-ide/scripts/ Won't run out of the box i guess, but it gives a good idea on how scripting CODESYS works.

adenis modified a comment on ticket #64

2023-04-16T20:20:41.633000Z

Thanks for the response! I am already building my libraries and packaging them in Jenkins. I am running SP17 so I can't take advantage of the SP19 feature. I'll have a look at bug 63. Ideally, the test results would be stored in the Jenkins build folder. This would allow concurrent running of builds. Really what I wanted to know is if someone could share the actual python script or include it in the library or in the documentation. In my experience, the largest challenge is to come up with what you...

adenis modified a comment on ticket #64

2023-04-15T22:12:43.263000Z

Thanks for the response! I am already building my libraries and packaging them in Jenkins. I am running SP17 so I cant take advantage of the SP19 feature. Ill have a look at bug 63. Really what I wanted to know is if you could share the actual python script or include it in the library or in the documentation. In my experience, the largest challenge is to come up with what you call: "your script file which monitors the xUnit xml-file has been dumped and exits CODESYS afterwards.py" If you have such...

adenis posted a comment on ticket #64

2023-04-15T22:11:50.193000Z

hermsen modified ticket #64

2023-04-15T21:34:15.579000Z

Jenkins python scripts

hermsen modified ticket #64

2023-04-15T21:33:53.205000Z

Jenkins python scripts

hermsen modified a comment on ticket #64

2023-04-15T21:33:19.573000Z

Hi, A small primer on how to go started. You should not change the path of the xml file via Python unless you fancy a challenge. Try changing via the supposed manner: via the new lib parameter interaction window (SP19 or newer) or change it in the .library and save it (recommended for older then SP19). The lib is open source so you may do whatever you see fit. I suggest you open the lib and explore/read it as this will help you write code for step2, monitoring the successful dump of the XML file...

hermsen modified ticket #64

2023-04-15T21:29:52.543000Z

Jenkins python scripts

hermsen posted a comment on ticket #64

2023-04-15T21:27:58.769000Z

adenis created ticket #64

2023-04-15T00:15:07.891000Z

Jenkins python scripts

hermsen modified a comment on ticket #63

2023-04-10T18:01:31.717000Z

you are most likely affected by this security fix: Codesys Advisory 2023-01 get the files from Program data or change that setting (Forceiecfilepath) to zero. hope this gives you enough hints

hermsen modified a comment on ticket #63

2023-04-10T17:58:19.145000Z

you are probably affected by this security fix: Codesys Advisory 2023-01

hermsen modified a comment on ticket #63

2023-04-10T17:16:13.571000Z

1) If you keep the default directory, is the file written? => The anwser should be YES if the unittest doesn't hang (i.e all test finish regardless outcome). 2) If you change the Default directory, is the file written? => If No: - check your PATH notation in CODESYS(!), - check the file write FB error messages, - check if the unittest doesn't hang (i.e all test finish regardless outcome). The XML file is only dumped at the end of all the tests. If the xml file is incomplete, assign a bigger filebuffer...

hermsen posted a comment on ticket #63

2023-04-10T17:12:45.932000Z

Its quite simple: the main fault was most probably somewhere in your filepath syntax. Read up on the FileRead/FileWrite/FileOpen and FileClose FB's from CAA File Library for hints on the path's syntax: CAA.FILENAME which is described in “CAA_Types.library“ should be usable for library “CAA_File“ in the following way. Separators between directory paths in “CAA.FILENAME“ are the slash („/“) or the back-slash („\“). The interpretation of the directory path is tolerant to the effect that either one or...

thecolonel26 modified a comment on ticket #63

2023-04-10T14:48:45.918000Z

Wait I found it. It seems it ignores the "C:\" I changed the path to just the file name 'coUnit_xunit_testresults.xml' and then I found it written to C:\ProgramData\CODESYS\CODESYSControlWinV3x64\B4A102F1\PlcLogic Is is rather confusing. Where is it writing to if I put C:\ on it? it says it is suceeding.

thecolonel26 posted a comment on ticket #63

2023-04-10T14:40:31.894000Z

Wait I found it. It seems it ignores the "C:\' and puts it in a temp folder in ProgramData C:\ProgramData\CODESYS\CODESYSControlWinV3x64\B4A102F1\PlcLogic Is is rather confusing.

thecolonel26 modified a comment on ticket #63

2023-04-10T14:28:12.453000Z

I am confused. As I said in my post 1. using the default directory which is set to 'C:\' in the library parameter list results in all log messages to the device log showing success. there are no error messages. 2. Changing the directory to C:\Temp\ has the same result all show sucess, and no error mesages. but the xml file is not there in either case. This is the export of the log entries runing the test using the default path ...

thecolonel26 modified a comment on ticket #63

2023-04-10T14:27:04.682000Z

thecolonel26 posted a comment on ticket #63

2023-04-10T14:26:07.420000Z

I am confused. As I said in my post 1. using the default directory which is set to 'C:\' in the library parameter list results in all log messages to the device log showing success. there are no error messages. 2. Changing the directory has the same result all show sucess, and no error mesages. but the xml file is not there in either case. This is the log entries with default path

hermsen posted a comment on ticket #63

2023-04-09T12:03:23.716000Z

1) If you keep the default directory, is the file written? => The anwser is YES if the unittest doesn't hang (i.e all test finish regardless outcome). 2) If you change the Default directory, is the file written? => If No: - check your PATH notation in CODESYS(!), - check the file write FB error messages, - check if the unittest doesn't hang (i.e all test finish regardless outcome). The XML file is only dumped at the end of all the tests. If the xml file is incomplete, assign a bigger filebuffer until...

hermsen modified ticket #62

2023-04-09T11:44:41.938000Z

Test Suite is not being Executed

thecolonel26 created ticket #63

2023-04-08T17:33:54.402000Z

xml Results file not being written to file system

thecolonel26 modified a comment on ticket #62

2023-04-08T17:29:25.848000Z

Ok it appears it will only execute once and then will require a reset and not just a start and stop. So I figured that out. Next problem This can be closed

thecolonel26 posted a comment on ticket #62

2023-04-08T17:29:02.859000Z

Ok it appears it will only execute once and then will require a reset and not just a start and stop. So I figured that out. Next problem

thecolonel26 created ticket #62

2023-04-07T17:08:40.050000Z

Test Suite is not being Executed

hermsen modified ticket #58

2022-12-10T18:49:10.063000Z

AssertResults array not checked for upper bounds

hermsen posted a comment on ticket #58

2022-12-10T18:48:45.836000Z

The library is open source, you can edit the source code if you wish.

hermsen modified ticket #58

2022-12-10T18:48:13.965000Z

AssertResults array not checked for upper bounds

sgronchi posted a comment on ticket #58

2022-11-29T13:47:58.032000Z

I had the same problem just today with coUnit v1.2.0.0. Library parameters are not editable so I cannot increment the related array size.

jtebokkel posted a review comment

2022-07-16T01:04:38.591000Z

I've caught so many bugs in my code. From silly mistakes to big head scratchers. Massive thanks guys

hermsen modified a wiki page

2022-06-24T19:37:07.078000Z

Userlist

hermsen modified a wiki page

2022-06-24T19:30:30.524000Z

Home

hermsen modified a wiki page

2022-05-24T23:47:44.971000Z

Home

hermsen modified ticket #60

2022-05-24T22:56:28.089000Z

AssertEquals_REAL does not handle NaN

hermsen modified ticket #60

2022-05-24T22:55:26.808000Z

AssertEquals_REAL does not handle NaN

hermsen modified ticket #60

2022-05-24T22:55:12.863000Z

AssertEquals_REAL does not handle NaN

hermsen modified a wiki page

2022-05-19T08:26:56.043000Z

Userlist

hermsen modified a comment on ticket #61

2022-05-18T16:47:06.622000Z

Hi, first off let me start by thanking you for using our unit testing framework solution. As you might know allready this software is an official fork of TcUnit. Therefore, we try to follow the original TcUnit codebase as close as possible or technically permitted. For instance, ADS will not work without a proper implementation in CODESYS, but a bespoke CI/CD runner is not necessary like in TwinCAT3. So there are pro's and con's. Currently we are waiting for the release of TcUnit v1.3 (or V2?). When...

hermsen posted a comment on ticket #61

2022-05-18T16:45:31.458000Z

Hi, first off let me start by thanking you for using our unit testing framework solution. As you might know allready this software is an official fork of TcUnit. Therefore, we try to follow the original TcUnit codebase as close as possible or technically permitted. For instance ADS will not work in CODESYS, but a bespoke CI/CD runner is not necessary like in TwinCAT3. So there are pro's and con's. Currently we are waiting for the release of TcUnit v1.3 (or V2?). When it is officially released, you...

stmos posted a comment on ticket #61

2022-05-18T10:55:30.941000Z

Attached a tentative solution for the problem, patch for the FB_AssertResultStatic.ReportResult method, based on what's implemented in FB_AssertArrayResultStatic.ReportResult.

stmos created ticket #61

2022-05-17T15:39:44.657000Z

FB_AssertResultStatic.ReportResult - PLC Crash

hermsen modified a wiki page

2022-04-17T22:54:26.734000Z

Home

hermsen modified a wiki page

2022-04-17T22:52:25.994000Z

Home

hermsen modified a wiki page

2022-04-17T22:49:57.192000Z

Home

jtebokkel posted a comment on ticket #60

2022-03-09T22:49:16.661000Z

See the attached files. Yes, this is in v1.2.0.0

hermsen modified ticket #60

2022-03-09T20:58:09.059000Z

AssertEquals_REAL does not handle NaN

hermsen posted a comment on ticket #60

2022-03-09T20:58:09.035000Z

Hi John, We are aware that certain details in the framework are sub optimal. However, that said, every tip/hint we get to optimise is one step in the right direction. So, since you found this issue, I hope you could also submit a patch which catches the Not A Number status and yields a fail in the assert. You can submit your patch in multiple ways. My suggestion would be that you just drop a code here in the Ticket. The reason behind this because I dont know if you hvae the Professional Developer...

jtebokkel modified a comment on ticket #60

2022-03-09T19:07:22.727000Z

A note about this. It seems that if all the variables in the function I'm testing are 0.0 then the math can return NaN however if only the divisor (rl2) is 0.0 then the controller will throw a divide-by-zero exception. FUNCTION ExampleFunction : REAL VAR_INPUT rl1 : REAL; rl2 : REAL; rl3 : REAL; END_VAR ExampleFunction := (rl1 / rl2) * rl3; It is interesting the things you discover as you create more test cases. (Thanks for your work on this library <3 )

jtebokkel posted a comment on ticket #60

2022-03-09T19:06:43.755000Z

A note about this. It seems that if all the variables in the function I'm testing are 0.0 then the math can return NaN however if only the divisor (r2) is 0.0 then the controller will throw a divide-by-zero exception. FUNCTION ExampleFunction : REAL VAR_INPUT rl1 : REAL; rl2 : REAL; rl3 : REAL; END_VAR ExampleFunction := (r1 / r2) * r3; It is interesting the things you discover as you create more test cases. (Thanks for your work on this library <3 )

jtebokkel created ticket #60

2022-03-09T17:40:43.551000Z

AssertEquals_REAL does not handle NaN

mr337 created ticket #59

2022-03-09T16:40:32.707000Z

FAQ page not working

hermsen modified ticket #58

2022-02-15T21:35:55.582000Z

AssertResults array not checked for upper bounds

hermsen modified a comment on ticket #58

2022-02-15T21:35:21.225000Z

Since I have not received feedback and you make use of an older version, I asume this has been resolved. If somehow your issue persists in the latest version ( v1.2) you can open a new ticket.

hermsen posted a comment on ticket #58

2022-02-13T21:03:40.502000Z

Since I have not received feedback and use an outdated version I asume this has been resolved. If somehow your issue persists in the latest version ( v1.2) you can open a new ticket.

hermsen modified a wiki page

2022-02-12T19:16:31.129000Z

Home

hermsen modified a wiki page

2022-02-12T19:15:43.680000Z

Home

hermsen modified a wiki page

2022-02-12T19:09:20.331000Z

Home

hermsen posted a comment on ticket #58

2022-02-08T21:08:11.863000Z

Thank you for using cfUnit. Sadly cfunit v1.1.0.0 will not receive bugfixes as it has been superseeded by coUnit. A slightly different name will only bring you some minor code changes if you use refactoring wisely, however coUnit v1.2.0.0 also brings new features, improvements and bugfixes over its predecessor. So step 1 is to update to coUnit.

srigan1986 created ticket #58

2022-02-08T17:30:25.217000Z

AssertResults array not checked for upper bounds

hermsen modified a wiki page

2022-02-05T22:42:47.057000Z

Home

hermsen committed [r459]

2022-02-01T09:51:47.088000Z

Autoversioning commit: a non-deltaV client made a change to

hermsen committed [r458]

2022-01-31T21:02:13.204000Z

Autoversioning commit: a non-deltaV client made a change to

hermsen committed [r457]

2022-01-31T21:02:02.742000Z

Autoversioning commit: a non-deltaV client made a change to

aliazzz created ticket #57

2022-01-09T11:13:18.113000Z

Create .yml pipeline and tuned manifest

hermsen posted a comment on ticket #55

2022-01-08T14:26:30.800000Z

Ignore my previous message. In the meanwhile I confirmed the real issue, now searching for root cause

aliazzz modified a comment on ticket #56

2022-01-05T06:52:05.119000Z

XSD https://forge.codesys.com/prj/cfunit/code/HEAD/tree/trunk/coUnit/XSD/JUnitv5.xsd Compliance https://forge.codesys.com/prj/cfunit/code/HEAD/tree/trunk/coUnit/XSD/QA%20xUnit.xml%20template.png?format=raw

aliazzz modified ticket #56

2022-01-05T06:51:26.594000Z

Add ability to disable tests and have them reported

aliazzz posted a comment on ticket #56

2022-01-05T06:50:12.407000Z

XSD https://forge.codesys.com/prj/cfunit/code/HEAD/tree/trunk/coUnit/XSD/JUnitv5.xsd Compliance (non debatable here) https://forge.codesys.com/prj/cfunit/code/HEAD/tree/trunk/coUnit/XSD/QA%20xUnit.xml%20template.png?format=raw

aliazzz posted a comment on ticket #56

2022-01-05T06:31:55.423000Z

Since this ticket is fulfilled within scope I will close the issue.

jtebokkel posted a comment on ticket #56

2022-01-05T00:56:50.996000Z

Did some digging on the format and I can't seem to find disabled as an attribute in the xsd (https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd) however skipped is mentioned, but in the context of

jtebokkel posted a comment on ticket #56

2022-01-05T00:33:10.713000Z

It seems it is not reported as disabled in the xml report or in the log. (See attached screen shots), but is reported as SKIPPED in the test suite. Maybe I misunderstand the disabled field for I was expecting that to give the total disabled or skipped tests. It does get marked as skipped, but calling TEST_FINISHED() doesn't mark it finished. (Not sure if it should)

aliazzz modified a comment on ticket #56

2022-01-04T21:28:52.281000Z

If you declare a test, calling TEST_FINISHED() is mandatory, even if the test will be disabled; TEST('DISABLED_ThisTestWillBeIgnored'); AssertEquals(Expected := a, Actual := b, Message := 'A does not equal B'); TEST_FINISHED(); Note that 'Disabled' is case insensitive.

aliazzz posted a comment on ticket #56

2022-01-04T21:25:07.699000Z

jtebokkel posted a comment on ticket #56

2022-01-04T19:57:03.692000Z

Does TEST_FINISHED() need to be called when the test is marked as disabled_? or is it sufficient to just have it marked as skipped/disabled? METHOD T101_Process VAR_INPUT END_VAR VAR_INST mxT : UINT; END_VAR IF xLiveDB THEN TEST('T101_Process'); ELSE // gc_sDisable : STRING(10) := 'disabled_'; TEST(concat(gConst.gc_sDisable, 'T101_Process')); // Is this call necessary? TEST_FINISHED(); RETURN; END_IF CASE mxT OF 0: // init mxT := 10; 10: // multi stage test mxT := 20; ELSE TEST_FINISHED(); END_C...

aliazzz modified ticket #56

2022-01-04T18:51:12.173000Z

Add ability to disable tests and have them reported

aliazzz posted a comment on ticket #56

2022-01-04T18:51:12.126000Z

Hi, maybe it is an undocumented feature(?) but your request is allready implemented into v1.2.0.0 :-) AFAIK Use Test('Disabled_TestXYZ'); Test_Finished(); This will be counted in the reporting as a skipped test. (both logged in PLC Log and in the XML.report)

jtebokkel created ticket #56

2022-01-04T17:30:54.236000Z

Add ability to disable tests and have them reported