View Issue Details

IDProjectCategoryView StatusLast Update
0004753CTT UA Scripts1 - Script Issuepublic2022-09-29 18:00
ReporterKarl Mayr Assigned ToYannik Klaass  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.03.501 
Summary0004753: Monitor Value Change Test case 022 aborts because of test case 020
Description

If the test case 020.js in the Monitored Item Services / Monitor Value Change ends with an error, then the test case 022.js also goes wrong.
This is a bug in test case 020.js. This test creates a MonitoredItem and no longer deletes it. For test case 022.js the limit is then 1 too low.

TagsNo tags attached.
Attached Files
Files Affected

maintree/Monitored Item Services/Monitor Value Change/Test Cases/020.js

Activities

Alexander Allmendinger

2019-09-02 08:10

developer   ~0010890

We tried to reproduce the issue on our test systems as well as reviewed the code of test script 020.js.
We can't find a way the script is printing an error and exists, excepts for a generic error catch. In order to identify the issue in the code, could you please provide the error output of script 020?

Paul Hunkar

2020-07-30 15:49

administrator   ~0012648

Send email to reporter - if no response will close as not repeatable

Karl Mayr

2020-07-31 06:30

reporter   ~0012649

I answered the questions of Alexander Allmendinger on 10.9.2019 by email already. See attachment 20190910_CTT_Report.pdf.
If 020.js is not executed, the 022.js is ok. See attachment 020.js.jpg in Debug Run1.
The error in 022.js only occures if 020.js goes wrong. See attachment 020.js.jpg in Debug Run2.
The 020.js goes wrong in this older version of OPC server because the BadNotSupported for IndexRange. See attachment 020.js-wireshark.jpg.

20190910_CTT_Report.pdf (93,642 bytes)
020.js.jpg (306,660 bytes)
020.js-wireshark.jpg (215,852 bytes)   
020.js-wireshark.jpg (215,852 bytes)   

Yannik Klaass

2022-09-06 13:26

developer   ~0017526

The error occurrs when the server returns an empty value in a PublishResponse. If toByteStringArray() gets called on this empty Value, the script returns an unexpected error when trying to access the result.
Code was extended to check if the returned value in the PublishResponse is empty before calling toByteStringArray() and print an error if it is.

Paul Hunkar

2022-09-29 16:01

administrator   ~0017900

reviewed issue in call, agreed to changes and closed issue

Issue History

Date Modified Username Field Change
2019-05-08 09:04 Karl Mayr New Issue
2019-05-23 14:33 Paul Hunkar Assigned To => Alexander Allmendinger
2019-05-23 14:33 Paul Hunkar Status new => assigned
2019-09-02 08:10 Alexander Allmendinger Status assigned => feedback
2019-09-02 08:10 Alexander Allmendinger Note Added: 0010890
2020-07-30 15:49 Paul Hunkar Note Added: 0012648
2020-07-31 06:30 Karl Mayr File Added: 20190910_CTT_Report.pdf
2020-07-31 06:30 Karl Mayr File Added: 020.js.jpg
2020-07-31 06:30 Karl Mayr File Added: 020.js-wireshark.jpg
2020-07-31 06:30 Karl Mayr Note Added: 0012649
2020-07-31 06:30 Karl Mayr Status feedback => assigned
2022-08-02 20:04 Paul Hunkar Project Compliance Test Tool (CTT) Unified Architecture => CTT UA Scripts
2022-09-06 13:26 Yannik Klaass Assigned To Alexander Allmendinger => Yannik Klaass
2022-09-06 13:26 Yannik Klaass Status assigned => resolved
2022-09-06 13:26 Yannik Klaass Resolution open => fixed
2022-09-06 13:26 Yannik Klaass Note Added: 0017526
2022-09-29 16:00 Paul Hunkar Files Affected => maintree/Monitored Item Services/Monitor Value Change/Test Cases/020.js
2022-09-29 16:01 Paul Hunkar Status resolved => closed
2022-09-29 16:01 Paul Hunkar Fixed in Version => 1.04.501
2022-09-29 16:01 Paul Hunkar Note Added: 0017900
2022-09-29 18:00 Paul Hunkar Fixed in Version 1.04.501 => 1.03.501