CTT test for A&C Acknowledge are skipped and giving error No alarms discoverd|OPC Certification and Interoperability Testing|Forum|OPC Foundation

Hi Prasad,

unfortunately without further details of the test run I can't really help identifying the reason for the skips in the testing. But in general the CTT and also the A&C Test Scripts are to help a tester executing the test cases automatically and therefore quickly. If, for whatever reason, test scripts cannot be executed on a product the testers in the certification test lab will execute the test cases manually. Of course this will result in increased testing time, but the test coverage would stay the same. So I would recommend to execute the skipped test cases manually (if they apply) and make sure your product handles all cases correctly. If during this investigation you'll notice issues in the scripts, we'd be happy to receive a bug report in our reporting tool (mantis.opcfoundation.org) and we'll try to fix the issue so with a future version of the CTT you can also execute the tests automatically.

I hope this helps.

Regards,
Alexander Allmendinger

Hello Prasad,

The test case descriptions available in the profile reporting tool (https://profiles.opcfoundation.org) are including all details about a test case and its execution. There are no additional documents or descriptions available for lab personnel.

When test cases are being skipped which should be executed, then we recommend to look at the test case description in the profile reporting tool and follow the testing steps to verify the product behaves correct manually. This needs to be done by utilizing an OPC UA Client / OPC UA Server combination which allows to execute the test cases. In case of having an OPC UA Server which needs to be exercised, you can use the UA Expert to connect to the server and verify the transmitted information are correct and pass the described test cases. Sometimes such checks will require to also use Wireshark during the test execution and verify the details transmitted on the wire.

Usually during such checks we’ll find some issues in the servers which have caused the scripts to be skipped. A known issue from some servers is for example, that they are created BranchIds for every occurrence of an alarm, while the specification requires that the current state always has the BranchId=null. If this is the case in your server too, that would be a misbehavior and would explain why those tests are being skipped. I hope you’ll find something during manual execution of the tests.

Regards,
Alexander Allmendinger