A collection of various Code Quality checks that are easy to use.
With the SloopTools Quality Checks, we want to improve the Code Quality of WinCC OA projects and offer a comprehensive service.
FREE version of CtrlPPCheck included in DEMO version!
Get more information below at the detailed description.
Microsoft Windows 7Microsoft Windows 10Microsoft Windows Server 2012 R2Microsoft Windows Server 2016
1.0.2 - Updats & new demo (2019-07-01)
900 / 900
Price: € 0,00
CtrlPPCheck is a variation of the well-known cppCheck that understands WinCC OA CTRL and CTRL++.
*"Upgrade / Year" entitles to download and use all versions of the add-on including minor and major features in the paid period. It will be automatically calculated
based on the total price. Charged per Year.
**"Upgrade once" entitles to download and use the latest versions of the add-on including minor and major features. It will be automatically calculated based on the
total price. Activated manually at a later point of time via the order page. Charged after activation.
The add-on Quality Check & CtrlPPCheck by SloopTools deals with Code Quality. Overall, code quality is important to software quality. And quality influences how safe and reliable your codebase is. High quality is of critical importance to many development teams today. This is particularly important for those who develop safety-critical applications, ie SCADA or HMI.
Furthermore, the integrity of the project is checked with the following checks:
Pictures used in the project
Overloaded files from the version, for maintenance purposes
Static code analysis ala cppCheck for WinCC OA CTRL in the GEDI
Included are, among many others, these checks:
Comparison is always true / false
Return value of a specific function is not used
e.g. return from dpExists ()
and other ...
With the SloopTools Quality Checks we want to improve the Code Quality of WinCC OA projects and offer a comprehensive service. The seamless integration into the development environment of WinCC OA (GEDI) was very important to us. The integration into the GEDI was carried out in the following places:
Drop-Down menu in the GEDI menu bar
Dock-Module for the GEDI with results
Script check via button in the script editor
Since this additional feature brings a lot of quality into the code as well as many potential programming errors and we will continue to evolve it but give everyone the opportunity to test, we provide 3 levels of licensing:
Quality Checks are included. CtrlPPCheck is not included. For full functionality, buy the CtrlPPCheck feature in the SloopTools Store
No or a FREE license is required for this.
CtrlPPCheck for script files and recursive project check are included. Limitations: Max. 1 error per error ID will be shown. For full functionality, buy the CtrlPPCheck feature in the SloopTools Store
To test the DEMO version you need a free "Try for 30 Days" demo license.
Script files with unlimited lines and an unlimited amount of files for recursive project check are included. All errors will be shown.
This version requires a FREE license with the additional feature "CtrlPPCheck" from the SloopTools Store. This must be purchased and activated via the installer.
WinCC OA CTRL Library Check (available since version 1.0.2)
All missing CTRL functions will be configured to check the number of arguments and return value
Own libraries check
Be able to configure and check arguments and return values from own libraries
Borders for quality control customizable
e.g. Lines per function, number of files in the directory, ...
Check your coding guidelines
e.g. Functions always begin with the prefix "xy_"
Create a report
HTML or PDF report for your quality assurance
Complete panel check
Including Ctrl + E and Scope-Lib
Currently on request
See complete documentation with all Limitations and the complete Roadmap on our documentation page:
Can I change the limits of the quality checks (e.g. lines per function, count of sub directories, …)?
Currently not but this is one of the features on our roadmap.
Can I train my own libraries so they will be included into the check?
Currently not but it’s one of the features on our roadmap
Why CTRL functions in libs will marked as not used but it’s right because I just define them there to use somewhere else?
Yes, that a current limitation and is on our roadmap
Why are some CTRL functions are not checked or marked as wrong but I am use I use them in a correct way?
That could be because at the current time we don’t have configured all WinCC OA CTRL functions. This will be updates asap.
Is this working on Linux?
Due to some technical reasons the SloopTools store currently doesn’t support Linux but if you want to use it on Linux, please get in contact with us. We can send it you directly.
For what WinCC OA versions I can use it?
It works for WinCC OA 3.15 and 3.16.
There are some errors reported that are not really errors in my code. Can I hide them?
Yes, you can hide a complete type of error or severity or make inline suppression for some specific lines. See more details in our documentation https://docu.slooptools.com
Can I start the check via command line for nightly builds or similar?
Yes, please have a look to our documentation and the chapter “CtrlPPCheck command line”
Which WinCC OA files I can check?
You can check all CTRL files (scripts, libs and panels). On panels you can check each event script of a panel on his own. To check the whole panel in the Script Editor (e.g.: Strg-E) is one of the features on our roadmap.
Is the CtrlPPCheck included in the FREE or DEMO version?
Yes, you can try the CtrlPPCheck with some limitations in the DEMO version. For more detailed see the part licenses in the detailed description above.