Post by aliazzz on #10 On using the RC versions of CfUnit
CfUnit
questions
(Post)
summary: on using the RC1.0.9.9 version of CfUnit --> On using the RC versions of CfUnit (see trunk)
Last updated: 2020-05-27
Post by aliazzz on #2 Which runtimes are supported?
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -21,5 +21,5 @@ ---------- | ---------- | ---------- | ---------- Schneider SoMachine | ? | verified | - ABB Automation Builder | v2.2.2 | verified | - -WAGO e!COCKPIT | ? | verified | Ticket[Tickets:#48] +WAGO e!COCKPIT | ? | verified | [Ticket:#48] ---------- | ---------- | ---------- | ----------
Last updated: 2020-07-15
Post by aliazzz on #2 Which runtimes are supported?
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -21,5 +21,5 @@ ---------- | ---------- | ---------- | ---------- Schneider SoMachine | ? | verified | - ABB Automation Builder | v2.2.2 | verified | - -WAGO e!COCKPIT | ? | verified | [Ticket:#48] +WAGO e!COCKPIT | ? | verified | [Tickets:#48] ---------- | ---------- | ---------- | ----------
Last updated: 2020-07-15
Post by aliazzz on #5 FAQ will be redirected 17:15:20 3-1-2020
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -2,6 +2,6 @@ Since tReason behind this decision is simple, time constraints. Plus, technically CfUnit is about 90% similair to TcUnit as most of the differences are internal framework functionalities, and not the user interactive parts. The same is true for the user-api. This will dissappear from the library and rediect to the original TcUnit API. The new FAQ will cover most basic and advanced topics of general usage. Offcourse some of these questions will relate to TwinCAT usage only, but mostly these questions and anwsers can easily be mapped to CODESYS. -Therefore, we recommended not post any questions here, but at https://tcunit.org/. The correct url of the new faq will be posted here, and afterwards this FAQ will be frozen. +Therefore, we recommended to visit https://tcunit.org/. Hoping to see you at the new FAQ at which hopefully you can find anwsers to any questions you might have! -Hoping to see you at the new FAQ at which hopefully you can find anwsers to any questions you might have! +*The correct url of the new faq will be posted here, and afterwards this FAQ will be frozen.* status: --> open
Last updated: 2019-12-31
Post by aliazzz on #3 Can I add extra stuff into the log?
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -2,5 +2,12 @@ Use the function **LogStr( msgprio, '...', '...' );** to add extra information into the log. -Prio INFO is recommended for this purpose as type ERROR is reserved [FUTURE] to generate a status report for a CI/CD toolchain xUnit (jUnit) xml report. +Priorities +INFO (1) : Recommened verbose message +WARNING (2) : +ERROR (4): ERROR is reserved [FUTURE] to generate a status report for a CI/CD toolchain xUnit (jUnit) xml report. +Usage example +~~~ +LogStr( 1, ' Extra log message: %s', xMyBool ); +~~~ status: --> open
Last updated: 2019-07-06
Post by aliazzz on #4 Jenkins or Drone integration?
CfUnit
questions
(Post)
status: --> closed
Last updated: 2019-08-07
Post by aliazzz on #10 On using the RC versions of CfUnit
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -1,6 +1,6 @@ For current projects it is highly encouraged to use the stable V1.0.0.0 official release of CfUnit. -However, for more the adventurous people a "Release Candidate" might do, but your mileage may vary! +However, for more the adventurous people a "Release Candidate" might do. Release Candidate are considered to be an advanced work in progress of the next expected public release. A Release Candidate code is not yet entirely field tested and may contain parts which need to be addressed further. If any problems are addressed, the Release Candidate will be upgraded to a higher version without prior notice. This cycle repeats itself until the software is considered 'mature' and receives a public release. If you decide to use an RC and you stumble upon something unexpected, please **share** your findings so we may improve the software further. Please do provide the following information so that we can replicate and address the problem accordingly; @@ -11,6 +11,9 @@ * What steps did you take, which resulted into the actual behaviour. * We can ask you to provide further information if needed. +The latest "Release Candidate" can be downloaded here; +https://forge.codesys.com/prj/cfunit/code/HEAD/tree/trunk/Library/CfUnit.library + Regards and have fun!
Last updated: 2020-05-27
Post by aliazzz on #2 Which runtimes are supported?
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -21,5 +21,5 @@ ---------- | ---------- | ---------- | ---------- Schneider SoMachine | ? | verified | - ABB Automation Builder | v2.2.2 | verified | - -WAGO e!COCKPIT | ? | verified | Ticket[48] +WAGO e!COCKPIT | ? | verified | Ticket [#48] ---------- | ---------- | ---------- | ----------
Last updated: 2020-07-15
Post by aliazzz on #11 IECStringUtils
CfUnit
questions
(Post)
status: --> closed
Last updated: 2020-06-08
Post by aliazzz on #2 Which runtimes are supported?
CfUnit
questions
(Post)
status: --> open discussion: enabled --> disabled
Last updated: 2019-06-03
Post by aliazzz on #2 Which runtimes are supported?
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -21,5 +21,5 @@ ---------- | ---------- | ---------- | ---------- Schneider SoMachine | ? | verified | - ABB Automation Builder | v2.2.2 | verified | - -WAGO e!COCKPIT | ? | verified | Ticket [#48] +WAGO e!COCKPIT | ? | verified | Ticket [48] ---------- | ---------- | ---------- | ----------
Last updated: 2020-07-15
Post by aliazzz on #10 On using the RC versions of CfUnit
CfUnit
questions
(Post)
summary: On using the RC versions of CfUnit (see trunk) --> On using the RC versions of CfUnit Description has changed: Diff: --- old +++ new @@ -6,7 +6,9 @@ If you decide to use an RC and you stumble upon something unexpected, please **share** your findings so we may improve the software further. Please do provide the following information so that we can replicate and address the problem accordingly; * Please check if the RC you use is latest RC available. Please upgrade and check if your issue persists. -* If your issue persists after update, describe the problem which caused you the send in your feedback. +* If your issue persists after update, describe the problem which caused you the send in your feedback here: +https://forge.codesys.com/prj/cfunit/tickets/ + * Please also provide the behaviour you expected, instead of what really occured, * What steps did you take, which resulted into the actual behaviour. * We can ask you to provide further information if needed.
Last updated: 2020-05-27
Post by aliazzz on #3 Can I add extra stuff into the log?
CfUnit
questions
(Post)
status: closed --> open
Last updated: 2019-08-07
Post by aliazzz on #2 Which runtimes are supported?
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -1,10 +1,7 @@ -**All CODESYS runtimes from v3.5.14.x or higher are supported without any known issues** -**OEM Runtimes listed (or higher) are supported, but mileage may vary, try at your own luck** +**CfUnit is verified on the following runtime versions (not exhaustive). If you have successfully ran CfUnit on a runtime system that is not yet listed here, please drop us an email and let us know so others can benefit from it too.** -Older runtime support may vary but in theory any runtime starting from 3.5.10.20 should work ( but your mileage may vary, try at your own luck). In case of such older runtimes, some library dependencies should be swapped for older ones. +Sadly, we cannot guarantee this library to be compatible with all systems, though we strive for high inter-compatibility. All vanilla CODESYS runtimes from v3.5.14.x or higher are supported. OEM runtimes listed (or higher) are supported, but mileage may vary. Older runtime support may vary but in theory any runtime starting from 3.5.10.20 should work ( but your mileage may vary, try at your own luck). In case of such older runtimes, some library dependencies should be swapped for older ones. -CfUnit is verified on following system versions (the list is not exhaustive). -If you have it running on your yet unlisted and it is not yet listed, please drop us a mail and we will add it to the list; System | Version | Result | Remark ---------- | ---------- | ---------- | ----------
Last updated: 2020-07-15
Post by aliazzz on #2 Which runtimes are supported?
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -18,7 +18,6 @@ CODESYS Control Linux SL | 3.5.15.x | verified | CODESYS Control Linux SL | 3.5.16.x | verified | CODESYS Control for BeagleboneBlack SL | 3.5.10.30 | verified | ----------- | ---------- | ---------- | ---------- Schneider SoMachine | ? | verified | ABB Automation Builder | v2.2.2 | verified | WAGO e!COCKPIT | ? | verified | [#48]
Last updated: 2020-07-15
Post by aliazzz on #2 Which runtimes are supported?
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -1,6 +1,6 @@ **CfUnit is verified on the following runtime versions (not exhaustive). If you have successfully ran CfUnit on a runtime system that is not yet listed here, please drop us an email and let us know so others can benefit from it too.** -Sadly, we cannot guarantee this library to be compatible with all systems, though we strive for high inter-compatibility. All vanilla CODESYS runtimes from v3.5.14.x or higher are supported. OEM runtimes listed (or higher) are supported, but mileage may vary. Older runtime support may vary but in theory any runtime starting from 3.5.10.20 should work ( but your mileage may vary, try at your own luck). In case of such older runtimes, some library dependencies should be swapped for older ones. +Sadly, we cannot guarantee this library to be compatible with all systems, though we strive for high inter-compatibility. All vanilla CODESYS runtimes from v3.5.14.x or higher are supported. OEM runtimes listed (or higher) are supported, but mileage may vary. Older runtime support in theory can work starting from 3.5.10.20 ( again, your mileage may vary, so try at your own luck). In case of older runtimes, some library references/dependencies should be swapped for older ones. System | Version | Result | Remark
Last updated: 2020-07-15
Post by aliazzz on #10 On using the RC versions of CfUnit
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -1,14 +1,14 @@ -For current projects it is highly encouraged to use the stable V1.0.0.0 official release of CfUnit. +# On using the RC versions of CfUnit -However, for more the adventurous people a "Release Candidate" might do. -Release Candidate are considered to be an advanced work in progress of the next expected public release. A Release Candidate code is not yet entirely field tested and may contain parts which need to be addressed further. If any problems are addressed, the Release Candidate will be upgraded to a higher version without prior notice. This cycle repeats itself until the software is considered 'mature' and receives a public release. +For the the slightly more adventurous people a "Release Candidate" can be installed in tandem next to V1.0.0.0 official public release of CfUnit. Release Candidate are considered to be an advanced work in progress in lieu of the next expected public release. A Release Candidate code is not yet entirely field tested and may contain parts of code which might need to be addressed. If any problems are addressed, the Release Candidate will receive an upgrade to a higher version (without prior notice). This cycle will repeat itself until the software is considered 'mature' and receives a public release. So with your help we can field test the software and thus limit the number of bug fixes needed after an official public release. If you decide to use an RC and you stumble upon something unexpected, please **share** your findings so we may improve the software further. Please do provide the following information so that we can replicate and address the problem accordingly; -* Please check if the RC you use is latest RC available. Please upgrade and check if your issue persists. +* Please check if the RC you use is latest RC available. Please **upgrade** to the latest RC and check if your issue persists. * If your issue persists after update, describe the problem which caused you the send in your feedback here: https://forge.codesys.com/prj/cfunit/tickets/ +* Provide the RC version you have encountered a problem in (should be the latest version ;-) ) * Please also provide the behaviour you expected, instead of what really occured, * What steps did you take, which resulted into the actual behaviour. * We can ask you to provide further information if needed.
Last updated: 2020-05-27
Post by aliazzz on #2 Which runtimes are supported?
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -1,21 +1,25 @@ -**All runtimes from v3.5.14.x or higher are supported without any known issues** +**All CODESYS runtimes from v3.5.14.x or higher are supported without any known issues** +**OEM Runtimes listed (or higher) are supported, but mileage may vary, try at your own luck** Older runtime support may vary but in theory any runtime starting from 3.5.10.20 should work ( but your mileage may vary, try at your own luck). In case of such older runtimes, some library dependencies should be swapped for older ones. CfUnit is verified on following system versions (the list is not exhaustive). If you have it running on your yet unlisted and it is not yet listed, please drop us a mail and we will add it to the list; -System | Version | Result +System | Version | Result | Remark +---------- | ---------- | ------ +CODESYS Control Win SL (x64) | 3.5.14.x | verified | - +CODESYS Control Win SL (x64) | 3.5.15.x | verified | - +CODESYS Control Win SL (x64) | 3.5.16.0 | verified | - +CODESYS Control for Raspberry Pi SL | 3.5.14.x | verified | - +CODESYS Control for Raspberry Pi SL | 3.5.15.x | verified | - +CODESYS Control for Raspberry Pi SL | 3.5.16.0| verified | - +CODESYS Control Linux SL | 3.5.14.x | verified | - +CODESYS Control Linux SL | 3.5.15.x | verified | - +CODESYS Control Linux SL | 3.5.16.x | verified | - +CODESYS Control for BeagleboneBlack SL | 3.5.10.30 | verified | - ---------- | ---------- | ------ -CODESYS Control Win SL (x64) | 3.5.16.0 | verified -CODESYS Control for Raspberry Pi SL | 3.5.16.0| verified +Schneider SoMachine | ? | verified | - +ABB Automation Builder | v2.2.2 | verified | - +WAGO e!COCKPIT | ? | verified | Ticket[48] ---------- | ---------- | ------ -CODESYS Control Win SL (x64) | 3.5.15.x | verified -CODESYS Control for Raspberry Pi SL | 3.5.15.x | verified ----------- | ---------- | ------ -CODESYS Control for Raspberry Pi SL | 3.5.14.x | verified -CODESYS Control Win SL | 3.5.14.x | verified -CODESYS Control Win SL (x64) | 3.5.14.x | verified -CODESYS Control Linux SL | 3.5.14.x | verified ----------- | ---------- | ------ -CODESYS Control for BeagleboneBlack SL | 3.5.10.30 | verified
Last updated: 2020-07-15
Post by aliazzz on #8 How can I disable or ignore a test?
CfUnit
questions
(Post)
Status: closed --> open
Last updated: 2020-05-01
Post by aliazzz on #4 Jenkins or Drone integration?
CfUnit
questions
(Post)
Currently a pre-alpha results.xml is generated.
Last updated: 2019-12-26
Post by aliazzz on #2 Which runtimes are supported?
CfUnit
questions
(Post)
status: open --> closed
Last updated: 2020-01-20
Post by aliazzz on #1 Which Codesys compiler version can I use at minimum? 19:33:12 28-6-2019
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -1,2 +1 @@ Recommended usage from **3.5.14.0 or higher**. -Lower versions are not recommended at this time. status: open --> closed discussion: enabled --> disabled
Last updated: 2019-06-06
Post by aliazzz on #7 Running a test over multple PLC cycles
CfUnit
questions
(Post)
Description has changed: Diff: --- old +++ new @@ -1,3 +1,9 @@ -You can accomplish this by instance the function block under test as an instance variable of the main body of the test-suite rather than in the test method itself. +See the provided example in the installation package for more details -See the provided example in the installation package for more details. +Or get CfUnitTimedTestExample.project from the trunk +Other versions of CfUnit are not supported, please update to v1.0.0.0 or latest RC; + +CfUnit v1.0.0.0 => Works, verified +CfUnit v1.0.9.94 (RC4) => Works, verified + +
Last updated: 2020-06-02
Post by aliazzz on #6 Log file Location
CfUnit
questions
(Post)
Hi, In version v1.0.0.0 there is no log in the filesystem. You can however, save the internal devicelog to the filesystem if you wish via the export log function. That way you can refernce the log and it's messages while the runtime is offline. From v1.1.0.0 (currently in development) an xunit compatible xml file can be exported which contains the entire log.
Last updated: 2020-01-20
Post by aliazzz on #8 How can I disable or ignore a test?
CfUnit
questions
(Post)
status: --> closed
Last updated: 2020-04-27