Testing
WinCC Open Architecture
For WinCC OA versions, dedicated validation pages exists: WinCC OA Validation
mono-vendor OPC UA
Every OPC-UA server release is tested in the lab according to a checklist, and the results documented on RTD (and published with the server release notification email)
- CAEN: https://readthedocs.web.cern.ch/display/ICKB/Versions
- ISEG: https://readthedocs.web.cern.ch/pages/viewpage.action?pageId=121604262
- Wiener: https://readthedocs.web.cern.ch/pages/viewpage.action?pageId=125045587
Examples of the check lists can be found from the pages above, for example for version 0.9.7 of the CAEN OPC UA server:
Moreover, these OPC-UA server have a suite of (googletest) C++ unit tests as part of their source code; the tests are built and run with every CI pipeline on linux & windows – the whole pipeline fails if any test fails.
multi-vendor OPC UA
- Lxi: lab tests with real hardware are done manually, the compatibility is then stated/updated in the Lxi server documentation (pipeline)
- PDU: tests with real hardware are done manually, the compatibility is then stated/updated in the PDU server documentation (pipeline)
Both codes are running through the C++-QA pipeline, no other validations are done, since both servers can be easily functionality-checked manually.
Fieldbuses
CANbus
- we have partially automated lab tests which require manual setup in the lab
- conformity and performance tests with CanModule are documented
- as part of gitlab CANX documentation (from pipeline),
- internal jenkins CANX jobs,
- additionally in RTD CanModule and RTD CANX-tester.
PLC
C++ static code analysis
the clang-tidy/cppcheck/kobe/sonarqube details of the C++-QA pipeline are documented in ics-fd-qa , producing these sonarqube results on the cental cvl instance .