View Issue Details

IDProjectCategoryView StatusLast Update
0009678CTT UA Test Case4 - Test Case Definitionpublic2024-09-19 14:00
ReporterStephanie Ackermann Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionno change required 
Product Version1.04.11.502 
Summary0009678: Historical Access Read Raw / 010.js: Fehler im Testskript. ContinuationPoint bei HistoryRead mit Bound=1
Description

In diesem Testfall (Test 1 und Test 4) wird ein HistoryRead mit folgenden Parametern aufgerufen:

  • StartTime = EndTime
  • Bound=True(1)
  • NumValuePerNode=1

Da Bound=True und NumValuePerNode=1 gesetzt ist wird vom zu testen Server ein ContinautionPoint zurückgegeben (da Bound=1 bedeutet, dass die Grenzen mit ausgegeben werden sollten, es also mind. 2 Values gibt: START und END + Werte dazwischen). Dies wird aber im Testfall als Fehler betrachtet.

Richtig wäre es einen ContinuationPoint zu erwarten und erst bei einer zweiten Abfrage (mit gesetztem ContinationPoint) keinen weiteren CP zu erwarten (da es bei StartTime=EndTime und Bound=true nur 2 Werte (START und END) geben kann).

TagsNo tags attached.
Files Affected

Activities

Paul Hunkar

2024-07-27 05:39

administrator   ~0021517

Translation -
In this test case (Test 1 and Test 4) a HistoryRead is called with the following parameters:

StartTime = EndTime
Bound=True(1)
NumValuePerNode=1
Since Bound=True and NumValuePerNode=1 are set, a ContinuationPoint is returned by the server to be tested (since Bound=1 means that the limits should be output, so there are at least 2 values: START and END + values ​​in between). However, this is considered an error in the test case.

It would be correct to expect a ContinuationPoint and not to expect another CP until a second query (with ContinationPoint set) (since there can only be 2 values ​​(START and END) with StartTime=EndTime and Bound=true).

Paul Hunkar

2024-09-19 13:59

administrator   ~0021748

The test case is correct - when starttime = endtime only one value is to be returned
from specification "It is specifically allowed for the startTime and the endTime to be identical. This allows the Client to request just one value. "
further more with regard to the bounds - the spec say the following - "If numValuesPerNode is 1 then only the start bound is returned (the end bound if the reverse order is needed)"
and by definition of a bounding value says a value at the starttime is to be returned.

The net result isa that only one value is returned and it has a timestamp of StartTime.

Paul Hunkar

2024-09-19 14:00

administrator   ~0021749

The test case is correct as written

Issue History

Date Modified Username Field Change
2024-07-23 08:46 Stephanie Ackermann New Issue
2024-07-27 05:39 Paul Hunkar Note Added: 0021517
2024-09-19 11:51 Paul Hunkar Assigned To => Paul Hunkar
2024-09-19 11:51 Paul Hunkar Status new => assigned
2024-09-19 13:59 Paul Hunkar Note Added: 0021748
2024-09-19 14:00 Paul Hunkar Status assigned => resolved
2024-09-19 14:00 Paul Hunkar Resolution open => no change required
2024-09-19 14:00 Paul Hunkar Note Added: 0021749