View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005437Compliance Test Tool (CTT) Unified Architecture3 - Feature Requestpublic2020-02-05 09:082020-04-30 14:25
ReporterSebastian Allmendinger Assigned ToSebastian Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.03.341.393 
Target Version1.03.341.394Fixed in Version1.03.341.394 
Summary0005437: Increment of DateTime values should be handled correct if the initial value was encoded as 0 or MaxInt64
Description

A DateTime value shall be encoded as a 64-bit signed integer (see Clause 5.2.2.2) which represents the number of 100 nanosecond intervals since January 1, 1601 (UTC).
Not all DevelopmentPlatforms will be able to represent the full range of dates and times that can be represented with this DataEncoding. For this reason, a number of rules shall be applied when dealing with date/time values that exceed the dynamic range of a DevelopmentPlatform.
If the encoded value of a DateTime variable is 0, the CTT is decoding that value to 1601-01-01 12:00:00AM and is incrementing that value. It may happen that the incremented value is still not in the valid range of the server and will still be encoded as 0. This value would not be the value expected by the CTT.

Additional Information

Because several test script are using the increment to cause data changes a correct handling of the DateTime datatype is required.
Suggestion: In case the server provides a value encoded as 0 or MaxInt64, the CTT should set the value to the actual Date / Time as that value should always be in the range of the server.

TagsNo tags attached.
Files Affected

Activities

Sebastian Allmendinger

2020-02-08 19:59

developer   ~0011567

Improved as suggested.

Paul Hunkar

2020-04-30 14:25

administrator   ~0012014

reviewed ion CMP call

Issue History

Date Modified Username Field Change
2020-02-05 09:08 Sebastian Allmendinger New Issue
2020-02-08 05:21 Paul Hunkar Assigned To => Alexander Allmendinger
2020-02-08 05:21 Paul Hunkar Status new => assigned
2020-02-08 19:59 Sebastian Allmendinger Assigned To Alexander Allmendinger => Sebastian Allmendinger
2020-02-08 19:59 Sebastian Allmendinger Status assigned => resolved
2020-02-08 19:59 Sebastian Allmendinger Resolution open => fixed
2020-02-08 19:59 Sebastian Allmendinger Fixed in Version => 1.03.341.394
2020-02-08 19:59 Sebastian Allmendinger Note Added: 0011567
2020-04-30 14:25 Paul Hunkar Status resolved => closed
2020-04-30 14:25 Paul Hunkar Note Added: 0012014