View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006157Compliance Test Tool (CTT) Unified Architecture4 - Test Case Definitionpublic2020-10-15 17:272021-04-01 15:37
ReporterMatthias Damm Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Fixed in Version1.03.341.397 
Summary0006157: A & C Refresh - Err-005 - expected result makes no sense
Description

Err-005
Test Case Description:
Create a data subscription and call refresh on it.

Test Requirements:
There are no monitored item in the subscription that support Events.

Expected Result:
Invocation fails.
ServiceResult = Good; OperationResults = BadSubscriptionIdInvalid

The expected result makes no sense since the subscription is valid. A result code should only handle one potential error scenario and BadSubscriptionIdInvalid is used if the passed in SubscriptionId is not valid.

There is currently no result defined for this case and therefore the servers just retun Good since everything is valid, there is just nothing to Refresh.

If we want to flag this an error, we need to introduce a new expected result in Part 9 like BadNothingToDo and describe this case in the description.

TagsNo tags attached.
Files Affected

Relationships

related to 0006158 closedPaul Hunkar 10000-009: Alarms and Conditions Should ConditionType::ConditionRefresh fail if the Subscription has no event monitored items 

Activities

Paul Hunkar

2020-10-22 16:59

administrator   ~0013081

this test case should be removed, when/If the refresh method in the alarm spec adds a specific code for this it can be added in again with an updated return code

Paul Hunkar

2020-10-22 17:01

administrator   ~0013082

when review scripts we found a miss-match in all err cases 002 thru 005 are off this test was in 002, 002 test was in 003 etc. This issue should also be fixed prior to release the scripts.

Alexander Allmendinger

2020-11-03 10:41

developer   ~0013105

Obsoleted the test case, as the described behavior is currently not defined in the spec.

Also fixed the order of the test cases.

Paul Hunkar

2021-04-01 15:37

administrator   ~0014157

Reviewed in CMP call , agreed to changes and closed

Issue History

Date Modified Username Field Change
2020-10-15 17:27 Matthias Damm New Issue
2020-10-15 17:33 Matthias Damm Relationship added related to 0006158
2020-10-22 16:58 Paul Hunkar Assigned To => Alexander Allmendinger
2020-10-22 16:58 Paul Hunkar Status new => assigned
2020-10-22 16:59 Paul Hunkar Note Added: 0013081
2020-10-22 17:01 Paul Hunkar Note Added: 0013082
2020-11-03 10:41 Alexander Allmendinger Status assigned => resolved
2020-11-03 10:41 Alexander Allmendinger Resolution open => fixed
2020-11-03 10:41 Alexander Allmendinger Fixed in Version => 1.03.341.397
2020-11-03 10:41 Alexander Allmendinger Note Added: 0013105
2021-04-01 15:37 Paul Hunkar Status resolved => closed
2021-04-01 15:37 Paul Hunkar Note Added: 0014157