View Issue Details

IDProjectCategoryView StatusLast Update
0003965Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2019-04-12 15:49
ReporterThomas Merk Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Fixed in Version1.03.341.381 
Summary0003965: SyntaxError in Address Space Model/Address Space Events/Test Cases/initialize.js
Description

In line 14 (and may be other lines) there is a syntax error, which causes a failure to be reported:

SyntaxError: Invalid return statement

TagsNo tags attached.
Files Affected

Relationships

related to 0004001 closedAlexander Allmendinger Address Space Events / initialize.js 

Activities

Paul Hunkar

2017-11-02 15:08

administrator   ~0008639

can you provide the version/Build number of the CTT, we are not seeing a syntax error?

Thomas Merk

2017-12-11 09:32

reporter   ~0008786

I do not remember the exact version.
It was definitely a 1.3.340.xxxx, most likely the newest available version (from share point) at theat date.

Bernd Edlinger

2017-12-11 10:51

reporter   ~0008787

This happens still with CTT generated from latest git:

Precondition is we have no TriggerNodes configured.
Base Eventing is selected.

The file: maintree/Base Eventing/Monitor Events/Test Cases/initialize.js
contains a syntax error at line: 8

include( "./library/ServiceBased/Helpers.js" );

const CUNAME="Monitor Events"

if (Test.Connect()) {
//Define trigger functions for the configured trigger Nodes
var eventTriggerItems = MonitoredItem.fromSettings(["/Server Test/NodeIds/Events/TriggerNode01", "/Server Test/NodeIds/Events/TriggerNode02"], undefined, Attribute.NodeClass);
if (!isDefined(eventTriggerItems) || eventTriggerItems.length === 0) { addSkipped("Not enough event trigger node items configured."); return (false); } <-- "return" is invalid here.

// determine the type of the triggers
if (!ReadHelper.Execute({ NodesToRead: eventTriggerItems })) { addError(&quot;Unable to read trigger nodes. Aborting test.&quot;); return (false); }

Alexander Allmendinger

2018-08-06 16:27

developer   ~0009272

This script already has been fixed for not making use of return statements.

Paul Hunkar

2019-04-12 15:49

administrator   ~0010182

Reviewed in CMP call - Actually should have been marked a duplicate of 4001

Issue History

Date Modified Username Field Change
2017-09-27 05:45 Thomas Merk New Issue
2017-11-02 15:08 Paul Hunkar Note Added: 0008639
2017-11-02 15:08 Paul Hunkar Assigned To => Paul Hunkar
2017-11-02 15:08 Paul Hunkar Status new => feedback
2017-12-11 09:32 Thomas Merk Note Added: 0008786
2017-12-11 09:32 Thomas Merk Status feedback => assigned
2017-12-11 10:51 Bernd Edlinger Note Added: 0008787
2018-08-06 16:27 Alexander Allmendinger Note Added: 0009272
2018-08-06 16:27 Alexander Allmendinger Status assigned => resolved
2018-08-06 16:27 Alexander Allmendinger Fixed in Version => 1.03.341.381
2018-08-06 16:27 Alexander Allmendinger Resolution open => fixed
2019-01-28 14:10 Paul Hunkar Category Script Issue => 1 - Script Issue
2019-04-05 15:58 Paul Hunkar Assigned To Paul Hunkar => Alexander Allmendinger
2019-04-12 15:47 Paul Hunkar Relationship added related to 0004001
2019-04-12 15:49 Paul Hunkar Status resolved => closed
2019-04-12 15:49 Paul Hunkar Note Added: 0010182