View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006983Compliance Test Tool (CTT) Unified Architecture3 - Feature Requestpublic2021-06-03 21:192021-10-15 15:18
ReporterAlexander Allmendinger Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.03.341.398 
Fixed in Version1.03.341.399 
Summary0006983: Introduce ServiceFault recognition
Description

In the scripts we currently do not have the information whether we received a ServiceFault or a UA Service Call response with a Bad ServiceResult. This information needs to be available in the scripts and a check needs to be added, as a Bad ServiceResult is only valid in a ServiceFault message.

TagsNo tags attached.
Files Affected

Relationships

related to 0007361 assignedAlexander Allmendinger Introduce ServiceFault recognition 

Activities

Alexander Allmendinger

2021-06-18 11:55

developer   ~0014582

Added a boolean for the indication as well as getIsServiceFault and setIsServiceFault functions to be called from the scripts to get this information.

Alexander Allmendinger

2021-09-30 15:17

developer   ~0015085

There is an issue with the session activation in certain cases with the current implementation which needs to be solved before release.

Alexander Allmendinger

2021-10-14 16:08

developer   ~0015181

Discussed in the CMP Meeting today:
Decided to include the changes while excluding the ServiceFault check for CreateSession, ActivateSession and CancleSession. We will clone this issue and track the enhancements for CreateSession, ActivateSession and CancleSession in the clone and traget the fix in the next release.

Alexander Allmendinger

2021-10-15 13:46

developer   ~0015185

Introduced the recognition of a ServiceFault vs. a valid Response with a Bad ServiceResult. This mantis will only introduce these checks for all service calls but the session services. The session services will be tracked in the related mantis 7361 and are scheduled to be added with the next CTT release.

Paul Hunkar

2021-10-15 15:18

administrator   ~0015186

reviewed updates in call, agreed to changes and closed

Issue History

Date Modified Username Field Change
2021-06-03 21:19 Alexander Allmendinger New Issue
2021-06-17 15:36 Paul Hunkar Assigned To => Alexander Allmendinger
2021-06-17 15:36 Paul Hunkar Status new => assigned
2021-06-18 11:55 Alexander Allmendinger Status assigned => resolved
2021-06-18 11:55 Alexander Allmendinger Resolution open => fixed
2021-06-18 11:55 Alexander Allmendinger Fixed in Version => 1.03.341.399
2021-06-18 11:55 Alexander Allmendinger Note Added: 0014582
2021-09-30 15:17 Alexander Allmendinger Status resolved => feedback
2021-09-30 15:17 Alexander Allmendinger Resolution fixed => reopened
2021-09-30 15:17 Alexander Allmendinger Note Added: 0015085
2021-10-14 16:08 Alexander Allmendinger Note Added: 0015181
2021-10-14 16:15 Paul Hunkar Issue cloned: 0007361
2021-10-14 16:16 Paul Hunkar Relationship added related to 0007361
2021-10-15 02:52 Paul Hunkar Status feedback => assigned
2021-10-15 13:46 Alexander Allmendinger Status assigned => resolved
2021-10-15 13:46 Alexander Allmendinger Resolution reopened => fixed
2021-10-15 13:46 Alexander Allmendinger Note Added: 0015185
2021-10-15 15:18 Paul Hunkar Status resolved => closed
2021-10-15 15:18 Paul Hunkar Note Added: 0015186