View Issue Details

IDProjectCategoryView StatusLast Update
0008564CTT UA Test Case4 - Test Case Definitionpublic2023-05-12 15:38
ReporterAlexander Allmendinger Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.03.09.501 
Fixed in Version1.03.09.501 
Summary0008564: A and C Comment / Err-006 asks for wrong OperationResult
Description

The test case expects to receive a Bad_NotSupported when calling AddComment for an EventId, which is not related to a condition. Because such an event has no ConditionId which can be used for the AddComment call, the script uses a known ConditionId from other events. It then uses the non-condition event as EventId and expects Bad_EventIdUnknown as OperationResult, what is the correct status code for this scenario (see Err-002).

As it is not possible to call AddComment without misusing a condition or providing a wrong condition, the test will always result in a Bad_EventIdUnknown or a Bad_NodeIdUnknown. The test case needs to be updated to the actual test scenario.

TagsNo tags attached.
Files Affected

Activities

Archie Miller

2023-01-09 21:21

administrator   ~0018446

I question the validity of this test. AddComment is mandatory for all alarm types, so its not possible to call this on an alarm that doesn't support AddComment

Paul Hunkar

2023-02-03 15:17

administrator   ~0018658

change test case to match script with Bad_EventIdUnknown

Also add another test case that uses an EventId from Condition1 and a ConditionId from condition2 (i.e. they do not match up) - should generate the same error

Alexander Allmendinger

2023-05-03 07:07

developer   ~0019265

Changed the expected result as described and added a second test step.

Paul Hunkar

2023-05-12 15:38

administrator   ~0019365

reviewed test case agreed to updated text closed issue

Issue History

Date Modified Username Field Change
2023-01-04 14:02 Alexander Allmendinger New Issue
2023-01-09 21:21 Archie Miller Note Added: 0018446
2023-02-03 15:13 Paul Hunkar Assigned To => Alexander Allmendinger
2023-02-03 15:13 Paul Hunkar Status new => assigned
2023-02-03 15:17 Paul Hunkar Note Added: 0018658
2023-05-03 07:07 Alexander Allmendinger Status assigned => resolved
2023-05-03 07:07 Alexander Allmendinger Resolution open => fixed
2023-05-03 07:07 Alexander Allmendinger Note Added: 0019265
2023-05-12 15:38 Paul Hunkar Status resolved => closed
2023-05-12 15:38 Paul Hunkar Fixed in Version => 1.03.09.501
2023-05-12 15:38 Paul Hunkar Note Added: 0019365