View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0008463CTT UA Test Case4 - Test Case Definitionpublic2022-11-25 12:392023-05-12 15:11
ReporterBernd Edlinger Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Fixed in Version1.03.09.501 
Summary0008463: Base Info Core Structure/001.js is now too strict
Description

Observed with Compliance Test Tool V1.04.11-01.00.501

Base Info Core Structure/001.js reports missing nodes, when Fully Exposed Type System is not checked
e.g. OperationLimitType -> MaxNodesPerHistoryReadData ==> [NOT FOUND] REQUIRED

But also when the Fully Exposed Type System is available, e.g. because of Embedded Server Profile,
the test fails, because our server implements the Node Set Version 1.04.9, and some additional nodes would be available in 1.04.11,

Note: we have a variable ns=0:i=15959
OpcUaId_OPCUANamespaceMetadata_NamespaceVersion
which could be read, and which should return the string "1.04.9"
Our expectation would be that the script gives only some kind of warnig for items that were added in later versions.

TagsNo tags attached.
Files Affected

Relationships

related to 0008655 assignedAlexander Allmendinger CTT UA Scripts Base Info Core Structure/001.js is now too strict 

Activities

Bernd Edlinger

2022-11-25 12:56

reporter   ~0018192

Note: If the Fully Exüpsed type system is selected there is an additioinal message, probably related to the nodeset version:

Error: Unable to find the TypeDefinition for 'i=24148' in the TypeSystem of the Server even though the 'Server Test/Fully Exposed Type System' is set.

Paul Hunkar

2023-01-26 17:34

administrator   ~0018596

In CMP Call - discussed this issue - need to add a test case that is run early - that checks the Nodeset version vs what the test is using designed for - generating an error is the CTT namespace version is newer then what the server is exposing in the NamespaceVersion - indicating that there is a miss match and that error might result.

Paul Hunkar

2023-01-26 17:36

administrator   ~0018599

need to add a test case for this

Alexander Allmendinger

2023-05-03 07:20

developer   ~0019267

Created test case 000 in Base Info Core Structure.

Paul Hunkar

2023-05-12 15:11

administrator   ~0019351

reviewed and updated test case in call, agreed to changes, closed issue

Issue History

Date Modified Username Field Change
2022-11-25 12:39 Bernd Edlinger New Issue
2022-11-25 12:41 Bernd Edlinger Description Updated
2022-11-25 12:56 Bernd Edlinger Note Added: 0018192
2023-01-26 17:34 Paul Hunkar Note Added: 0018596
2023-01-26 17:35 Paul Hunkar Issue cloned: 0008655
2023-01-26 17:35 Paul Hunkar Relationship added related to 0008655
2023-01-26 17:35 Paul Hunkar Project Compliance Test Tool (CTT) Unified Architecture => CTT UA Test Case
2023-01-26 17:36 Paul Hunkar Note Added: 0018599
2023-01-26 17:36 Paul Hunkar Assigned To => Alexander Allmendinger
2023-01-26 17:36 Paul Hunkar Status new => assigned
2023-01-26 17:37 Paul Hunkar Assigned To Alexander Allmendinger => Paul Hunkar
2023-05-03 07:20 Alexander Allmendinger Assigned To Paul Hunkar => Alexander Allmendinger
2023-05-03 07:20 Alexander Allmendinger Status assigned => resolved
2023-05-03 07:20 Alexander Allmendinger Resolution open => fixed
2023-05-03 07:20 Alexander Allmendinger Note Added: 0019267
2023-05-12 14:47 Paul Hunkar Category 1 - Script Issue => 4 - Test Case Definition
2023-05-12 15:11 Paul Hunkar Status resolved => closed
2023-05-12 15:11 Paul Hunkar Fixed in Version => 1.03.09.501
2023-05-12 15:11 Paul Hunkar Note Added: 0019351