0006468: NodeManagementDeleteNode / Err-002.js add node failes because of wrong for loop

ID	Project	Category	View Status	Date Submitted	Last Update

0006468	CTT UA Scripts	1 - Script Issue	public	2021-02-05 17:09	2022-08-25 03:09

Reporter	Maximilian	Assigned To	Alexander Allmendinger
Priority	normal	Severity	minor	Reproducibility	always
Status	assigned	Resolution	open
Platform	x86	OS	Windows	OS Version	10

Summary	0006468: NodeManagementDeleteNode / Err-002.js add node failes because of wrong for loop
Description	In the first round of the for(z) loop the for(i) add the maximum number of nodes to the NodesToAdd array and sends the call with the AddNodeIdsHelper. But in the second round of the for(z) loop the for(i) adds again the maximum number of nodes to the NodesToAdd array. So now the array has twice the size of supported nodes. This causes the second call of the AddNodeIdsHelper will fail. (In my oppinion the Status code should be Bad_TooManyOperations instead of Bad_EncodingLimitsExceeded) Also the test does not delete all nodes correctly. I have problems with following tests.
Tags	No tags attached.

Files Affected

Date Modified	Username	Field	Change
2021-02-05 17:09	Maximilian	New Issue
2021-02-19 16:41	Paul Hunkar	Assigned To	=> Paul Hunkar
2021-02-19 16:41	Paul Hunkar	Status	new => acknowledged
2021-02-19 16:41	Paul Hunkar	Note Added: 0013755
2022-08-18 14:36	Paul Hunkar	Assigned To	Paul Hunkar => Alexander Allmendinger
2022-08-18 14:37	Paul Hunkar	Status	acknowledged => assigned
2022-08-18 14:37	Paul Hunkar	Note Added: 0017331
2022-08-18 14:40	Paul Hunkar	Relationship added	related to 0006450
2022-08-25 03:09	Paul Hunkar	Project	Compliance Test Tool (CTT) Unified Architecture => CTT UA Scripts

Paul Hunkar 2021-02-19 16:41 administrator ~0013755	Agreed that this is an issue, but in general the NodeManagement test cases need a review

Paul Hunkar 2022-08-18 14:37 administrator ~0017331	We should just dump the nodemanagement test cases to a spreadsheet and review them in a call