View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005668Compliance Test Tool (CTT) Unified Architecture2 - CTT Binarypublic2020-05-27 16:502020-06-12 15:34
ReporterPaul Hunkar Assigned ToAlexander Allmendinger  
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.04.09.394 
Fixed in Version1.03.341.396 
Summary0005668: Multi dimension array related!
Description

As multi-dimensional array is supported now we started testing with that. To keep things simpler first, we configured only one 2 dimensional byte array, with the value like below:
Value Rank: 2
Array Dimensions 2*5 (Rows : 2, Columns: 5)
Values:
1 2 3 4 5
6 7 8 9 10

From my understanding of the spec, if only one element, Say 2nd element from the 2nd row then index range which will be passed is [1,1].

I have captured only those failed test cases and attached the CTT results so that it can be viewed in the CTT. As well as I have captured the wireshark.

Following test cases are failing:
Attribute_read_test_32:
Here, it is mentioned that it needs 2nd element from 2nd but requesting 2nd element from 1st row.

Steps To Reproduce

Create the 2 dimensional array and configure in CTT and run the Attribute services.

Additional Information

This issue was broken out of an issue that that had multiple items in it (5654 show original submitter)

TagsNo tags attached.
Files Affected

Activities

Paul Hunkar

2020-05-27 16:51

administrator   ~0012123

The description should not point to a specific element, since the test is just testing access to a n element that is not the fist element.

Alexander Allmendinger

2020-06-04 13:14

developer   ~0012180

Text has been updated to not described the used element to be more flexible:
Use of IndexRange for reading a single element of a multi-dimensional array. This test will be done for each data-type.

Paul Hunkar

2020-06-12 15:34

administrator   ~0012251

reviewed in CMP call

Issue History

Date Modified Username Field Change
2020-05-27 16:50 Paul Hunkar New Issue
2020-05-27 16:50 Paul Hunkar Issue generated from: 0005654
2020-05-27 16:51 Paul Hunkar Note Added: 0012123
2020-05-27 16:52 Paul Hunkar Additional Information Updated
2020-05-27 16:52 Paul Hunkar Assigned To => Alexander Allmendinger
2020-05-27 16:52 Paul Hunkar Status new => assigned
2020-06-04 13:14 Alexander Allmendinger Status assigned => resolved
2020-06-04 13:14 Alexander Allmendinger Resolution open => fixed
2020-06-04 13:14 Alexander Allmendinger Fixed in Version => 1.03.341.396
2020-06-04 13:14 Alexander Allmendinger Note Added: 0012180
2020-06-12 15:34 Paul Hunkar Status resolved => closed
2020-06-12 15:34 Paul Hunkar Note Added: 0012251