This feature would be very much needed. It is basically the only thing that is blocking use of Codesys GIT and preventing us from buying the lisences... Please, provide atleast a shcedule for this.
Hello, I've been busy with other stuff for a while but now this issue is again on the table. Yes, it is requirement from system architecture that unit tests are not implemented inside the library, so it is not doable for me. I also think that it is good practise since we want to keep the library 'clean'. Now back to my original problem. I want to call every FB and method defined in library-under-testing. I have defined another library (don't know whats the benefit of having a library instead of project)...
Hello, I need to implement unit tests for a library and to do that efficiently I also need to have access to on-public POUs inside the library. Unit tests cannot be inside the library. I found this page from Online help (https://help.codesys.com/webapp/properties;product=LibDevSummary;version=3.5.17.0) which indicates that there is UnitTestingDefine definition that could be used for changing the visibility during compilation. Some more info in here (https://help.codesys.com/webapp/visibility;product=LibDevSummary;version=3.5.17.0)...
I need to implement unit tests for a library and to do that efficiently I also need to have access to on-public POUs inside the library. Unit tests cannot be inside the library. I found this page from Online help (https://help.codesys.com/webapp/properties;product=LibDevSummary;version=3.5.17.0) which indicates that there is UnitTestingDefine definition that could be used for changing the visibility during compilation. Some more info in here (https://help.codesys.com/webapp/visibility;product=LibDevSummary;version=3.5.17.0)...
Unit tests in separate CODESYS-project