wiki Discussion ^{jebates31 wiki (Discussion)}
Forum for wiki comments
Last updated: 2021-07-15

(no subject) ^{jebates31 wiki (Thread)}
Last updated: 2021-07-15

Post by hermsen on #4 Jenkins or Drone integration? ^{co♻e: A unittest framework for CODESYS questions (Post)}
Description has changed: Diff: --- old +++ new @@ -1,2 +1,2 @@ -We aim to support both popular CI/CD platforms. -Jenkins/Drone testreport are supported through a xUnit.xml file. +We aim to support all popular CI/CD platforms. As long as your platform can consume xUnit compatible testfiles you wont experience any issues. Our framework generates a xUnit testreport each time a full test has run and is saved to a directory of your choice. +Just let your runner consume this file and you are all set. status: open --> closed assigned_to: h-hermsen
Last updated: 2021-07-15

blog Discussion ^{salahtmam blog (Discussion)}
Forum for blog comments
Last updated: 2021-07-15

co♻e: A unittest framework for CODESYS SVN repository ^{co♻e: A unittest framework for CODESYS code (SVN Repository)}
Last updated: 2021-07-15

Home ^{salahtmam wiki (WikiPage)}
This is the personal project of salahtmam. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2021-07-15

wiki Discussion ^{salahtmam wiki (Discussion)}
Forum for wiki comments
Last updated: 2021-07-15

(no subject) ^{salahtmam wiki (Thread)}
Last updated: 2021-07-15

Post by hermsen on #10 On using the RC versions of CfUnit ^{co♻e: A unittest framework for CODESYS questions (Post)}
status: open --> closed
Last updated: 2021-07-16

Ticket #10: On using the RC versions of CfUnit ^{co♻e: A unittest framework for CODESYS questions (Ticket)}
On using the RC versions of CfUnit A "Release Candidate" can be installed in tandem with V1.0.0.0 official public release of CfUnit and swapped in/out as you see fit. "Release Candidates" are considered to be advanced work in progress in lieu of the next expected public release. A "Release Candidate" has had limited field testing and may contain parts of code which might need to be addressed further. If any problems are addressed, the "Release Candidate" will receive an upgrade to a higher version without prior notice. This development cycle repeats itself until the software is considered mature and receives a true public release (web portal update, new .package, documentation, etc, etc). So, with your help, we can let the software get mature faster and limit the amount of bugsfixes needed after an official public release so we bring the pain forward and we can enjoy the gain sooner. We highly encourage you to use an RC and if you stumble upon something unexpected, please share your findings so we may improve the software faster. 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. Always 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. Regards and have fun! The CfUnit project team2021-07-16 14:54:37.563000 Ticket #10: On using the RC versions of CfUnit co♻e: A unittest framework for CODESYS cfunit qna questions False /prj/cfunit/questions/10/ Ticket On using the RC versions of CfUnit False 12 2020-05-01 10:29:29.948000 10 On using the RC versions of CfUnit closed On using the RC versions of CfUnit A "Release Candidate" can be installed in tandem with V1.0.0.0 official public release of CfUnit and swapped in/out as you see fit. "Release Candidates" are considered to be advanced work in progress in lieu of the next expected public release. A "Release Candidate" has had limited field testing and may contain parts of code which might need to be addressed further. If any problems are addressed, the "Release Candidate" will receive an upgrade to a higher version without prior notice. This development cycle repeats itself until the software is considered mature and receives a true public release (web portal update, new .package, documentation, etc, etc). So, with your help, we can let the software get mature faster and limit the amount of bugsfixes needed after an official public release so we bring the pain forward and we can enjoy the gain sooner. We highly encourage you to use an RC and if you stumble upon something unexpected, please share your findings so we may improve the software faster. 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. Always 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. Regards and have fun! The CfUnit project team False False 0 0 0 None aliazzz None
Last updated: 2021-07-16

Post by hermsen on #4 Jenkins or Drone integration? ^{co♻e: A unittest framework for CODESYS questions (Post)}
Description has changed: Diff: --- old +++ new @@ -1,2 +1,2 @@ -We aim to support all popular CI/CD platforms. As long as your platform can consume xUnit compatible testfiles you wont experience any issues. Our framework generates a xUnit testreport each time a full test has run and is saved to a directory of your choice. +We aim to support all popular CI/CD platforms. As long as your platform can consume xUnit compatible testfiles you wont experience any issues. The framework generates a xUnit compatible testreport each time a full test has run and is saved to a directory of your choice. Just let your runner consume this file and you are all set.
Last updated: 2021-07-16

Ticket #4: Jenkins or Drone integration? ^{co♻e: A unittest framework for CODESYS questions (Ticket)}
We aim to support all popular CI/CD platforms. As long as your platform can consume xUnit compatible testfiles you wont experience any issues. The framework generates a xUnit compatible testreport each time a full test has run and is saved to a directory of your choice. Just let your runner consume this file and you are all set.2021-07-16 14:53:24.972000 Ticket #4: Jenkins or Drone integration? co♻e: A unittest framework for CODESYS cfunit qna questions False /prj/cfunit/questions/4/ Ticket Jenkins or Drone integration? False 8 2019-08-07 20:06:00.559000 4 Jenkins or Drone integration? closed We aim to support all popular CI/CD platforms. As long as your platform can consume xUnit compatible testfiles you wont experience any issues. The framework generates a xUnit compatible testreport each time a full test has run and is saved to a directory of your choice. Just let your runner consume this file and you are all set. False False 0 0 0 None aliazzz hermsen
Last updated: 2021-07-16

(no subject) ^{co♻e: A unittest framework for CODESYS questions (Thread)}
Last updated: 2021-07-16

(no subject) ^{co♻e: A unittest framework for CODESYS questions (Thread)}
Last updated: 2021-07-16

cfunit: Artifact 60f19fb1c2e53b4af0920316 ^{co♻e: A unittest framework for CODESYS questions (Generic Artifact)}
Last updated: 2021-07-16

cfunit: Artifact 60f19dd5c2e53b4af09202da ^{co♻e: A unittest framework for CODESYS questions (Generic Artifact)}
Last updated: 2021-07-16

(no subject) ^{co♻e: A unittest framework for CODESYS questions (Thread)}
Last updated: 2021-07-16

Post by hermsen on #14 What are the notable differences between cfUnit and TcUnit? ^{co♻e: A unittest framework for CODESYS questions (Post)}
Description has changed: Diff: --- old +++ new @@ -6,4 +6,4 @@ TcUnit-Runner generates xUnit reporting file | co-Unit generates xUnit reporting file * ADS Transport layer | ADS not implemented and not supported -* Both TcUnit and co-Unit can generate this file, but in TcUnit results are transported via ADS to the runner. The xUnit report is then generated from the test results instead in the PLC. +* Both TcUnit and co-Unit can generate this file, but in coUnit it's usage is mandatory. Since TcUnit results are transported via ADS to its bespoke runner, the TcUnit xUnit report is generated from the ADS transmitted test results. No significant differences between these reports are expected.
Last updated: 2021-07-16

First steps with CODESYS Git (version 47) discussion ^{hermsen blog (Thread)}
First steps with CODESYS Git (version 47) discussion
Last updated: 2021-07-16

First steps with CODESYS Git (version 35) discussion ^{hermsen blog (Thread)}
First steps with CODESYS Git (version 35) discussion
Last updated: 2021-07-16

First steps with CODESYS Git (version 23) discussion ^{hermsen blog (Thread)}
First steps with CODESYS Git (version 23) discussion
Last updated: 2021-07-16

First steps with CODESYS Git (version 54) discussion ^{hermsen blog (Thread)}
First steps with CODESYS Git (version 54) discussion
Last updated: 2021-07-16

First steps with CODESYS Git (version 39) discussion ^{hermsen blog (Thread)}
First steps with CODESYS Git (version 39) discussion
Last updated: 2021-07-16

First steps with CODESYS Git (version 26) discussion ^{hermsen blog (Thread)}
First steps with CODESYS Git (version 26) discussion
Last updated: 2021-07-16

First steps with CODESYS Git (version 33) discussion ^{hermsen blog (Thread)}
First steps with CODESYS Git (version 33) discussion
Last updated: 2021-07-16

Sort by relevance or date