View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0008375Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2022-09-30 10:182024-09-18 19:45
ReporterJunaid M Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityrandom
Status resolvedResolutionno change required 
Summary0008375: Base Information > Base Info Resend Data Method > 2.js Fails Randomly
Description

In CTT tool version 1.04.11, the test case 002.js defined under Base Information > Base Info Resend Data Method passes randomly.
When the case fails it gives below error:
Expected to receive a value for each MonitoredItem again after calling ResendData. Expected <1> but got <0>.

Additional Information

When creating a subscription if we set below values we don't get above error while it does fails.
TC_Variables.TestSubscription.PublishingInterval = 500;
TC_Variables.TestSubscription.MaxKeepAliveCount = 10;

The script fails with error message:
Expected to receive the same value after calling ResendData than in last Publish because a new Sample should not be present yet.

TagsNo tags attached.
Files Affected

Activities

Junaid M

2022-10-06 09:18

reporter   ~0017957

The Script reads the server's current time twice. If the value is not same for both consecutive calls then it fails.
Script compares the current time values along with second and millisecond. Since second and millisecond part can vary between two consecutive request they can be ignored for comparing two responses.

Paul Hunkar

2022-11-03 15:34

administrator   ~0018095

Need to check if sampling interval is being honored, if not then server issue, if honoring (or revising) then the script could have an issue

Alexander Allmendinger

2023-05-04 13:55

developer   ~0019276

I looked at the script but it uses the RevisedIntervals for its calculations, so I'm not sure where the script misbehaves. I also tried to reproduce the issue but wasn't able to do so. Could you provide me your CTT settings xml, so I can try to reproduce it and see where the issue comes from?

Alexander Allmendinger

2024-09-18 19:45

developer   ~0021746

Issue was set to feedback for 2 years. Since no further feedback was provided, it is closed with no change required.

Issue History

Date Modified Username Field Change
2022-09-30 10:18 Junaid M New Issue
2022-10-06 09:18 Junaid M Note Added: 0017957
2022-11-03 15:27 Paul Hunkar Status new => feedback
2022-11-03 15:29 Paul Hunkar Assigned To => Paul Hunkar
2022-11-03 15:29 Paul Hunkar Status feedback => new
2022-11-03 15:34 Paul Hunkar Note Added: 0018095
2022-11-03 15:34 Paul Hunkar Assigned To Paul Hunkar => Alexander Allmendinger
2022-11-03 15:34 Paul Hunkar Status new => assigned
2023-05-04 13:55 Alexander Allmendinger Status assigned => feedback
2023-05-04 13:55 Alexander Allmendinger Note Added: 0019276
2024-09-18 19:45 Alexander Allmendinger Status feedback => resolved
2024-09-18 19:45 Alexander Allmendinger Resolution open => no change required
2024-09-18 19:45 Alexander Allmendinger Note Added: 0021746