View Issue Details

IDProjectCategoryView StatusLast Update
0007512Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2022-01-29 15:02
ReporterAlexander Allmendinger Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionwon't fix 
Product Version1.03.341.400 
Fixed in Version1.03.341.401 
Summary0007512: Data Access Percent Deadband / 008: Generated values may not cause a DataChangeNotification
Description

The script is generating values which are not supposed to pass the deadband in the beginning of the script. Those generated values are required to be different from the previous but not to be unique in the set. As a result it may happen that the values are repeated e.g. 26, 27 and 26 which is not problematic for the second step of the test but in the last step the script tries those values again while expecting DataChangeNotification for every value. But in this example case writing 26 as new value over the existing value 26 will not cause a DataChangeNotification no matter of the deadband value specified and therefore make the script fail.

TagsNo tags attached.
Files Affected

Relationships

related to 0007520 assignedAlexander Allmendinger CTT UA Test Case Monitor Basic needs new test case to validate ModifyMonitoredItem filter behavior 
related to 0007521 assignedAlexander Allmendinger CTT UA Test Case Monitored Items Deadband Filter needs new test case to validate ModifyMonitoredItem filter behavior 
related to 0007522 assignedAlexander Allmendinger CTT UA Test Case Data Access PercentDeadband needs new test case to validate ModifyMonitoredItem filter behavior 

Activities

Alexander Allmendinger

2022-01-04 10:01

developer   ~0015659

Implemented resetting the values before executing the last testing step.

Alexander Allmendinger

2022-01-06 13:03

developer   ~0015674

This issue has been discussed in the UA Working Group on 4th of January 2022.
There is a agreement, that a filter needs to be (re-)applied on a value when it is changed by calling ModifyMonitoredItem. Another acceptable behavior would be to always send the current value after a ModifyMonitoredItem service call.
Following this expectation from the UA Working Group this change is reverted and will not be part of the released CTT. In addition we will be adding a test case exercising this case. The new test case will be tracked in a new Mantis Issue.

Alexander Allmendinger

2022-01-06 15:32

developer   ~0015676

In CMP Call today:
Decided to create a test cases in:

  • Monitor Basic: Verify that a ModifyMonitoredItem is triggering a DataChangeNotification or reapplying the filter
  • Monitored Items Deadband Filter: Change the AbsoluteDeadband filter and verify it is reapplied on the current value
  • Data Access PercentDeadband: Change the PercentDeadband filter and verify it is reapplied on the current value

Alexander Allmendinger

2022-01-06 16:16

developer   ~0015677

New issues to create the test cases have been created.

Paul Hunkar

2022-01-29 15:02

administrator   ~0015893

Agreed to status and new issues -

Issue History

Date Modified Username Field Change
2022-01-03 23:25 Alexander Allmendinger New Issue
2022-01-04 06:35 Paul Hunkar Assigned To => Alexander Allmendinger
2022-01-04 06:35 Paul Hunkar Status new => assigned
2022-01-04 10:01 Alexander Allmendinger Status assigned => resolved
2022-01-04 10:01 Alexander Allmendinger Resolution open => fixed
2022-01-04 10:01 Alexander Allmendinger Fixed in Version => 1.03.341.401
2022-01-04 10:01 Alexander Allmendinger Note Added: 0015659
2022-01-06 13:03 Alexander Allmendinger Status resolved => feedback
2022-01-06 13:03 Alexander Allmendinger Resolution fixed => reopened
2022-01-06 13:03 Alexander Allmendinger Note Added: 0015674
2022-01-06 15:32 Alexander Allmendinger Note Added: 0015676
2022-01-06 16:14 Alexander Allmendinger Relationship added related to 0007520
2022-01-06 16:14 Alexander Allmendinger Relationship added related to 0007521
2022-01-06 16:14 Alexander Allmendinger Relationship added related to 0007522
2022-01-06 16:16 Alexander Allmendinger Status feedback => resolved
2022-01-06 16:16 Alexander Allmendinger Resolution reopened => won't fix
2022-01-06 16:16 Alexander Allmendinger Note Added: 0015677
2022-01-29 15:02 Paul Hunkar Status resolved => closed
2022-01-29 15:02 Paul Hunkar Note Added: 0015893