Ticket search results

Test Suite is not being Executed

thecolonel26 — Sun, 09 Apr 2023 11:44:41 -0000

My Test Suite is not being Executed. I have went through the [tutorial](https://forge.codesys.com/lib/counit/tutorial/Tutorial/) Several times and I can not figure out what is wrong. CoUnit.RUN(); gets called I can put a break point before and after it. but my test suite body is never called ~~~ PROGRAM PRG_Test VAR inst_Test_Wago_750_455 : Test_Wago_750_450; END_VAR CoUnit.RUN(); //** This is called ~~~ ~~~ FUNCTION_BLOCK Test_Wago_750_450 EXTENDS CoUnit.FB_TestSuite VAR_INPUT END_VAR VAR_OUTPUT END_VAR VAR END_VAR InputEqualsZero(); //** Never reached ~~~ ~~~ METHOD InputEqualsZero VAR module : Wago_750_455; processImage : DWORD; i : INT; buffer_False : BOOL := FALSE; buffer_Four : REAL := 4; END_VAR ~~~ ~~~ //TEST(__POUNAME()); TEST('Test'); processImage := 0; FOR i := 0 TO 3 BY 1 DO module.Param_ProcessImage[i] := processImage; module.Cfg_HasDiagBits := TRUE; module(); AssertEquals(Expected := buffer_Four, Actual := module.ValueAs_mA[i], Message := 'The calculation is not correct'); AssertEquals(Expected := buffer_False, Actual := module.Error_Any[i], Message := 'Message (Figure me Out Later)'); AssertEquals(Expected := buffer_False, Actual := module.Error_UnderRange[i], Message := 'Message (Figure me Out Later)'); AssertEquals(Expected := buffer_False, Actual := module.Error_OverRange[i], Message := 'Message (Figure me Out Later)'); END_FOR TEST_FINISHED(); ~~~ And Export of my Project is attached

AssertResults array not checked for upper bounds

srigan1986 — Sat, 10 Dec 2022 18:49:10 -0000

I use the CfUnit testframework (not yet CoUnit) and run loop over indexed test cases with TRY, CATCH on the testee FB. At some point of time, exception occured and it was showing the method AssAssertResult as the culprit for exception - RTS_ACCESS_VIOLATION. I suspect if it could be a phenomenon when the number of asserts per testsuite exceed 1000 (MaxNumberOfAssertsForEachTestSuite). I have attached screenshots of code snippets. Please verify if it could be the cause of exception and would be glad to hear from you.

Add ability to disable tests and have them reported

jtebokkel — Wed, 05 Jan 2022 06:51:26 -0000

It would be nice to add the ability to disable tests and have them listed in the xml report and logger report. I've got a situation where I have a some function blocks that I want to test. Most of the functionality can be tested in quick tests that only take a cycle or two, but some tests are dealing with timeouts that can make the test suite run for a few minutes. I'd like to be able to setup two configurations (through applications) that will disable the longer running tests so that I can quickly iterate my code. I have an input to my test suite function block that I can set to disable the longer running tests, but I have no easy way to know how many disabled tests there are when I run the quick config. If we could disable tests with a reason that would be even better. Then I could write a test for a future feature and have it shown as disabled rather than just failing before the feature is written. Thanks so much for the work that has gone into this project. It is really helpful and I greatly appreciate it.

Migrate project to /lib/counit

i-campbell — Thu, 30 Sep 2021 20:23:29 -0000

migrate project * [x] create project * [x] export/import webpages * [x] import SVN

Unit tests in separate CODESYS-project

pasi-p-sand — Fri, 16 Jul 2021 15:03:33 -0000

I have implemented unit tests code-to-test.library. Unit testing code is written into code-to-test_UnitTests.project. I found that it is only possible to call public POUs from the library. Is there a way around this limitation? I found that there is possibility to define UnitTestingDefine in Codesys application which would cause PRIVATE, INTERNAL, PROTECTED and FINAL keywords to be ignored during UnitTest application compilation. Is there an example how to utilize this feature?

Multiple timed tests, assertions and access violations

stmos — Tue, 10 Aug 2021 01:49:14 -0000

HI all, I've started looking at the framework for a project for which I wanted to use TDD techniques. Using the public version 1.1.0.0, after some tests I started having AccessViolations on assertions or static variables that do not get initialized with expected init values... What I've deduced and what it's not clear to me for timed tests (state-machine based): * If I have too many assertions in a test this causes an access violation in the PLC (using Codesys Control Win x86). If I have a state in the test state machine with an assert that is called repeatedly on each cycle (for example because I want to check that a boolean does not get true for some cycles) at some point I get an AccessViolation exception and the PLC stops. I've found a way around to call asserts only once in case a specific condition happens. Is that true? * For timed tests it seems from the examples that for a test suite we can have only one test case. If I use more than one test case I get strange behaviors, like tests failing for wrong reasons... I've put static variables on each test case with the unit under test also. Always in the examples I've found that the UUT and other support variables are instead instantiated in the FB of the test suite. Which one is the correct way to do it? * When I need to use TEST_FINISHED vs TEST_FINISHED_NAME? I get strange behaviors also here. If I name the test in only the first (init) state of the test case test machine I must then used TEST_FINISHED_NAME, but then failed assertions do not appear in the log... Thanks in advance for the help. Regards.

Download To Wago 750-841

terry56 — Fri, 19 Mar 2021 06:39:31 -0000

Can I download a project from a Wago 750-841 that I do not have project for?

Refactor anything "CfUnit" into "cfUnit"

hermsen — Mon, 09 Aug 2021 20:13:36 -0000

#49 Refactor anything "CfUnit" into "cfUnit"

Porting the library to e!COCKPIT (from WAGO)

pedro — Tue, 14 Jul 2020 08:27:21 -0000

I've tried to port the library as it is to e!COCKPIT (WAGO's version of CODESYS V3) to use it in my projects. First, I did a test with CODESYS V3 in a Raspberry Pi, just following the tutorial to see and understand how the library is supposed to work. After that, I installed the library in e!COCKPIT and ran the example of the tutorial. As far as I'm able to assess with my limited knowledge about the inner functioning of the library and the used components (CmpLog, CmpApp...): - It seems like the tests ran properly, as you can see in the attached screenshot (CfUnit_WAGO_ejemplo.PNG). - But the messages don't appear in the CfUnit logger. Trying to solve this problem or make the library works somehow in e!COCKPIT I've been tinkering a bit with the code while reading through CODESYS Online Help. The only solution I've found is really a shabby workaround, but it works: I've change the piece of code you can see in the in the attached screenshot (AddLogEntry_change.png). This ignores the CfUnit logger that the library creates and write the messages in the successfully. This is enough for me to be able to leverage the benefits of having a unit test framework within my development tool. I hope this ticket is helpful to someone out there trying to use the library with WAGO software and also curious about the initial problem: do you have any clue about why the CfUnit logger is not working? P.S. - Thank you very much for porting this into CODESYS from TcUnit. I'm sure is going to be very helpful to me.

Move Ticket #38 to Tickets > Admin - Tickets > Options > Help text to display on ticket list pages

i-campbell — Fri, 12 Jun 2020 17:20:23 -0000

Info in Ticket #38 might be more visible if moved to Tickets > Admin - Tickets > Options > Help text to display on ticket list pages At least, something helpful there linking to the important info on posting

Tutorial example not working as expected

lukasstelzer — Sat, 11 Jul 2020 08:55:56 -0000

I updated to latest RC version 1.0.9.94 After updating my lib in my project from version 1.0.0.0 the Variable NumberOfTests of my instance of FB_Sum_Test is always 0.. I have exactly the same setting as it is described in the tutorial with the FB_Sum..

add a contribution.md

aliazzz — Mon, 15 Jun 2020 22:09:14 -0000

*This is a first draft for review, please submit any feedback =) * # Contributing to CfUnit We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's: Reporting a bug Discussing the current state of the code Submitting a fix Proposing new features Becoming a maintainer ## We Develop with CODESYS Forge We use CODESYS Forge to host code, to track issues & feature requests. Since CODESYS IDE is currently only using SVN, Pull Requests (PR's) are a bit of an issue currently. Every code should be checked before submission: - Does your code have a test in the verifier? - No => write a test for the verifier - Yes => provide proof that your code and test works - After peer review and a working unittest in the verifier is provided, the code is eligible for merge in the trunk. ## Any contributions you make will be under the MIT Software License In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern. ## Report bugs using Codeys Forge [Tickets] We use Tickets to track public bugs. Report a bug by [opening a new ticket](https://forge.codesys.com/prj/cfunit/tickets/new); it's that easy! ## Write bug reports with detail, background, and sample code **Great Bug Reports** tend to have: - A quick summary and/or background - Steps to reproduce - Be specific! - Give sample code if you can. - What you expected would happen - What actually happens - Notes (possibly including why you think this might be happening, or stuff you tried that didn't work) ## Use a Consistent Coding Style * Never open/edit the trunk code! Instead, create a (local) branch under your own name and make your code adjustmensts there. * Make sure to keep the library settings and project information as the trunk project, except your version number. * Make sure that your CODESYS IDE uses spaces instead of tabs. The default behaviour of the CODESYS IDE is to use tabs so it needs to be changed. See Tools - Options - Text Editor - Editing - Untick "Keep tabs" and set tabwidth to 4 ## License By contributing, you agree that your contributions will be licensed under its MIT License. ## References This document was adapted from briandk's excellent [contribution guidelines template](https://gist.github.com/briandk/3d2e8b3ec8daf5a27a62).

CfUnit Logger shows count of only one Test Suite's Tests

i-campbell — Sun, 31 May 2020 22:54:35 -0000

cfUnit version 1.0.9.9 CODESYS IDE version SP16 CODESYS environment CODESYS Control Win x64 SP16 [compare strings](https://forge.codesys.com/u/i-campbell/comparestrings/) shows an example of 2 test suites each with 8 tests. The output from the logger shows: ~~~ Failed Tests: 0 Successful Tests: 8 Tests: 8 Test suites: 2 ~~~ I expected 16, like so: ~~~ Failed Tests: 0 Successful Tests: 16 Tests: 16 Test suites: 2 ~~~ the .\testresults.xml shows all tests, as I expected. Please see attached log and testresult

Implement support for WSTRING datatype

aliazzz — Wed, 27 May 2020 12:53:26 -0000

Currently datatype WSTRING is not supported. This point will be addressed in a future release by support for T_MaxWString AIias WSTRING(1024).

testresults.xml top level failure count not accurate

jtebokkel — Mon, 04 May 2020 19:30:32 -0000

On running multi-cycle tests the top level failure count is not accurate. I've attached reports. The one I induced a failure on a single cycle test. Both have a failure in a multi-cycle test ~~~ ... ... ~~~ total failures should be 2 in the pasted parts of the report.

Multi-cycle TestSuite not able to finish

jtebokkel — Mon, 04 May 2020 19:29:58 -0000

1. Bug Present as of this commit: https://forge.codesys.com/svn/prj,cfunit,code@362 When running tests that take multiple cycles to complete the test runner stops early. If there is more than one test suite in the project. For instance i have an SQL block I'm testing that takes several calls before it returns results. Tracked down the source of the bug to ```FB_CfUnitRunner.RunTestSuiteTests``` see the attached diff for the fix.

Property "Placeholder" should be set to "CfUnit"

aliazzz — Fri, 01 May 2020 09:43:32 -0000

I think the errors with CfUnit in my library, are because there is no placeholder set in the cfunit.library as described in https://help.codesys.com/webapp/checklist;product=LibDevSummary;version=3.5.15.0 10:11 Property "Placeholder" should be set to "CfUnit"

CmpLog generates errors in standard log, it won't show the CfUnit Log

aliazzz — Fri, 01 May 2020 09:43:32 -0000

Sometimes, but not always the following message shows up in the Device Log. It severly hampers usage of the CfUnit testing Framework as we cannot look at the CfUnit Log. ~~~ Description=Scheduler Tick [2] Operation: CmpID=0x00000019, ID=0x1, enable=1, alive=0, timeout=10000 [FAILED] ~~~ Why can't we display the CfUnit Log anymore? Find out root cause, Suggest fix, Implement fix.

Release v1.1.0.0

aliazzz — Mon, 12 Oct 2020 19:07:22 -0000

Release v1.1.0.0

The {attribute 'call_after_init'} is not necessary anymore

aliazzz — Fri, 01 May 2020 09:43:32 -0000

The {attribute 'call_after_init'} is not necessary for the test suites in the current implementation of TcUnit. Everything works without it - it was only necessary in the original implementation. The FB_TestSuite function block has no methods that are call_after_init, and it extends no function blocks, thus it's just an unnecessary leftover. The use of this attribute for test suites should be removed from the examples, documentation, and the verifier tests.

Documentation missing

aliazzz — Thu, 30 Sep 2021 20:22:56 -0000

Documentation missing for AssertArray2dEquals_LREAL AssertArray2dEquals_REAL AssertArray3dEquals_LREAL AssertArray3dEquals_REAL AssertArrayEquals_LREAL AssertArrayEquals_REAL Add in Online and Offline API documentation

Find or create a Codesys solution for: PVOID

aliazzz — Sat, 27 Jul 2019 18:23:32 -0000

~~~ TYPE PVOID : UDINT; END_TYPE ~~~

Find or create a Codesys solution for: E_ArgType

aliazzz — Sat, 27 Jul 2019 18:23:48 -0000

~~~ TYPE E_ArgType : ( ARGTYPE_UNKNOWN := 0, ARGTYPE_BYTE, ARGTYPE_WORD, ARGTYPE_DWORD, ARGTYPE_REAL, ARGTYPE_LREAL, ARGTYPE_SINT, ARGTYPE_INT, ARGTYPE_DINT, ARGTYPE_USINT, ARGTYPE_UINT, ARGTYPE_UDINT, ARGTYPE_STRING, ARGTYPE_BOOL, ARGTYPE_BIGTYPE, ARGTYPE_ULARGE, ARGTYPE_UHUGE, ARGTYPE_LARGE, ARGTYPE_HUGE, ARGTYPE_LWORD ); END_TYPE ~~~

Ticket search results

Test Suite is not being Executed

AssertResults array not checked for upper bounds

Add ability to disable tests and have them reported

Migrate project to /lib/counit

Unit tests in separate CODESYS-project

Multiple timed tests, assertions and access violations

Download To Wago 750-841

Refactor anything "CfUnit" into "cfUnit"

Porting the library to e!COCKPIT (from WAGO)

Move Ticket #38 to Tickets > Admin - Tickets > Options > Help text to display on ticket list pages

Tutorial example not working as expected

add a contribution.md

See also Ticket #43 TEST_FINISHED_NAMED sets finished flag and immediately clears it

See Also Ticket #44 - Testsuite with more than one multi-cycle tests won't finish

CfUnit Logger shows count of only one Test Suite's Tests

Implement support for WSTRING datatype

testresults.xml top level failure count not accurate

Multi-cycle TestSuite not able to finish

Property "Placeholder" should be set to "CfUnit"

CmpLog generates errors in standard log, it won't show the CfUnit Log

Release v1.1.0.0

The {attribute 'call_after_init'} is not necessary anymore

Documentation missing

Find or create a Codesys solution for: PVOID

Find or create a Codesys solution for: E_ArgType