View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006611CTT UA Scripts1 - Script Issuepublic2021-03-11 08:372022-08-25 03:09
ReporterCamille Guérin Assigned ToAlexander Allmendinger  
PrioritynormalSeveritymajorReproducibilityalways
Status assignedResolutionopen 
Summary0006611: Subscription Services/Subscription Publish Min 02/003.js wrong behavior when WriteResponse returns GoodCompleteAsynchronously
Description

This test case is not behaving normally when the OPC UA Server returns the status code GoodCompleteAsynchronously to the WriteRequest of the OPC UA Client.
When the OPC UA Server returns GoodCompleteAsynchronously it wait 5s after receiving the WriteResponse to send the first PublishRequest
When the OPC UA Server returns Good it directly send the PublishRequest after receiving the WriteResponse

When the OPC UA Server returns GoodCompleteAsynchronously, the test case end with the following error:
Publish() #4 (RequestHandle: 16) response did not complete within the expected time-frame.
Expected a value greater than <9500> and less than <10500>; but received <4975>.

When the OPC UA Server returns Good, the test case always end with Passed.

See the attached screenshot of a Wireshark capture.
On the left the run with the OPC UA Server returning WriteResponse GoodCompleteAsynchronously, on the right Good.
The Time column display the time between the Seconds since previous displayed packet.

TagsNo tags attached.
Attached Files
3_writeresponse_async.jpg (546,086 bytes)
Files Affected

Activities

Camille Guérin

2021-03-11 08:38

reporter   ~0014026

Product Version is 1.04.09.396

Camille Guérin

2021-03-11 13:31

reporter   ~0014031

I now found out that there is an options in the test settings to set the delay after GoodCompleteAsynchronously.
By default the value was 5000 that caused the error. Setting it to 100ms seems to resolve the issues.

Alexander Allmendinger

2021-03-18 15:54

developer   ~0014044

In the test script we should check the setting for the delay and calculate the intervals based on this setting.
If this is not possible, skip the test case if the delay is to big for the test case to be executed.

Paul Hunkar

2022-08-05 15:44

administrator   ~0017306

discussed in CMP - we decided that for a server that report GoodCompleteAsynchronously - the result should be a skip. The test can be run manually by the tester (either using a point that does not respond with GoodCompleteAsynchronously. or using a variable that is updated periodically or anything else the tester can figure out

Issue History

Date Modified Username Field Change
2021-03-11 08:37 Camille Guérin New Issue
2021-03-11 08:37 Camille Guérin File Added: 3_writeresponse_async.jpg
2021-03-11 08:38 Camille Guérin Note Added: 0014026
2021-03-11 13:31 Camille Guérin Note Added: 0014031
2021-03-18 15:53 Alexander Allmendinger Assigned To => Alexander Allmendinger
2021-03-18 15:53 Alexander Allmendinger Status new => assigned
2021-03-18 15:54 Alexander Allmendinger Status assigned => acknowledged
2021-03-18 15:54 Alexander Allmendinger Note Added: 0014044
2022-08-05 15:44 Paul Hunkar Note Added: 0017306
2022-08-05 15:44 Paul Hunkar Status acknowledged => assigned
2022-08-25 03:09 Paul Hunkar Project Compliance Test Tool (CTT) Unified Architecture => CTT UA Scripts