View Issue Details

IDProjectCategoryView StatusLast Update
0007353Compliance Test Tool (CTT) Unified Architecture4 - Test Case Definitionpublic2021-10-29 16:12
Reporterepetrevska@de.pepperl-fuchs.com Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
OSUbuntuOS Version20.04 
Product Version1.04.09.398 
Fixed in Version1.03.341.399 
Summary0007353: BaseInfo ServerCapabilities MaxNodesPerXXX tests are executed when value is set to 0
Description

The tests MaxNodesPer(Read, Write, HistoryReadData...) are executed also if the value is 0. In the OPC Foundation Profile Description, it says in the Test Case Ids 8 and above:
" Run this test if MaxNodesPerRead exists and is not 0", namely to run the test only if this value is not 0 or it exists.
https://profiles.opcfoundation.org/v104/Reporting/testcases/Server/BaseInfoServerCapabilities.html

In the testing tool, when the value is 0, it is set to the max. available value:

var realValue = itemMaxLen.Value.Value.toUInt32();
if( realValue === 0 ) {
addWarning( "MaxNodesPerRead is set to zero. It should be set to a realistic value. OperationLimit will be limited to this value." );
realValue = MAX_ALLOWED_SIZE;
}

Am I misunderstanding something or this is a small bug?

TagsNo tags attached.
Files Affected

Activities

Paul Hunkar

2021-10-15 15:33

administrator   ~0015189

The test case needs to remove the statement related to 0 - test case are good as is.

Alexander Allmendinger

2021-10-15 15:59

developer   ~0015191

Test cases have been updated to remove the precondition with checking for the 0. When an OperationLimit does not apply because the feature is not supported, this OperationLimit needs to be removed from the OperationLimit instance in the server object instance.

Updated test cases:
001, 002, 003, 004, 006a, 007a, 008, 009, 010, 011, 012, 013, 014, 015, 016, 017, 018, 019

Paul Hunkar

2021-10-29 16:12

administrator   ~0015243

reviewed test cases - agreed to update and close

Issue History

Date Modified Username Field Change
2021-10-11 10:50 epetrevska@de.pepperl-fuchs.com New Issue
2021-10-15 15:32 Paul Hunkar Assigned To => Alexander Allmendinger
2021-10-15 15:32 Paul Hunkar Status new => assigned
2021-10-15 15:33 Paul Hunkar Category 1 - Script Issue => 4 - Test Case Definition
2021-10-15 15:33 Paul Hunkar Note Added: 0015189
2021-10-15 15:59 Alexander Allmendinger Status assigned => resolved
2021-10-15 15:59 Alexander Allmendinger Resolution open => fixed
2021-10-15 15:59 Alexander Allmendinger Fixed in Version => 1.03.341.399
2021-10-15 15:59 Alexander Allmendinger Note Added: 0015191
2021-10-29 16:12 Paul Hunkar Status resolved => closed
2021-10-29 16:12 Paul Hunkar Note Added: 0015243