View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004975Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2019-08-24 19:102020-05-22 14:53
ReporterTim Fortin Assigned ToSebastian Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version1.03.341.390 
Target Version1.03Fixed in Version1.03.341.391 
Summary0004975: CTT not correctly checking for GoodCompletesAsynchronously status
Description

Issue is in the write.js file in directory Library->AttributeServiceSet -> Write.js.

On line 374 this code was written:

writeResponse.Results[i].StatusCode.StatusCode == StatusCode.GoodCompletesAsynchronously

but, in order to actually pull the status code off the writeResponse I had to use

writeResponse.Results[i].StatusCode == StatusCode.GoodCompletesAsynchronously

Also an important note is that 2 * the sampling interval wait time was not enough to sufficiently pass the tests. This is done on line 378.

Would it be a requirement to be able to asynchronously write then read a value in under 2 * the sampling interval fastest value?

TagsNo tags attached.
Files Affected

Relationships

related to 0005588 closedSebastian Allmendinger CTT not correctly checking for GoodCompletesAsynchronously status 

Activities

Paul Hunkar

2019-08-30 14:23

administrator   ~0010818

First part is an issue and should just be fixed

Second part - the time when the return is GoodCompletesAsynchronously should be either an very long time or should be configurable for how long to wait- this should be checked in all places where an write operation occurs - not just in the write tests that have been fixed

Alexander Allmendinger

2019-09-02 17:51

developer   ~0010902

First part of the issue has been fixed and will be part of the next build which is 1.03.341.390.
The setting to configure the delay will be provided in the next version of the CTT.

Sebastian Allmendinger

2020-05-08 14:54

developer   ~0012035

The changes made to the CTT work as expected. The same changes must also be made in another function. For more information, see MantisId 5588.

Paul Hunkar

2020-05-22 14:53

administrator   ~0012103

reviewed in CMP call

Issue History

Date Modified Username Field Change
2019-08-24 19:10 Tim Fortin New Issue
2019-08-30 14:12 Paul Hunkar Assigned To => Alexander Allmendinger
2019-08-30 14:12 Paul Hunkar Status new => assigned
2019-08-30 14:23 Paul Hunkar Note Added: 0010818
2019-09-02 17:51 Alexander Allmendinger Note Added: 0010902
2019-09-13 15:16 Paul Hunkar Target Version => 1.03
2019-11-04 15:04 Alexander Allmendinger Status assigned => resolved
2019-11-04 15:04 Alexander Allmendinger Resolution open => fixed
2019-11-04 15:04 Alexander Allmendinger Fixed in Version => 1.03.341.391
2020-04-23 13:29 Sebastian Allmendinger Status resolved => feedback
2020-04-23 13:29 Sebastian Allmendinger Resolution fixed => reopened
2020-04-23 17:50 Paul Hunkar Issue cloned: 0005588
2020-04-23 17:50 Paul Hunkar Relationship added related to 0005588
2020-04-23 17:50 Paul Hunkar Status feedback => assigned
2020-05-08 14:54 Sebastian Allmendinger Assigned To Alexander Allmendinger => Sebastian Allmendinger
2020-05-08 14:54 Sebastian Allmendinger Status assigned => resolved
2020-05-08 14:54 Sebastian Allmendinger Resolution reopened => no change required
2020-05-08 14:54 Sebastian Allmendinger Note Added: 0012035
2020-05-22 14:53 Paul Hunkar Status resolved => closed
2020-05-22 14:53 Paul Hunkar Note Added: 0012103