View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006089Compliance Test Tool (CTT) Unified Architecture4 - Test Case Definitionpublic2020-09-29 07:082021-04-01 14:43
ReporterMatthias Damm Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.04.09.397 
Summary0006089: Clarification [Subscription Client Basic] [Err-010] sequence number handling
Description

The expected results for this test case make no sense. They even require dangerous handling for a parameter that is information only for the client.

A client is responsible for acknowledging sequence numbers of processed notification messages (sequence number in the NotificationMessage).
It makes no sense to acknowledge any sequence number from the availableSequenceNumbers parameter since the client does not know the status of them.

In addition the behavior was recently updated in Part 4 to resolve the issues 0005634 and 0004795. This change will be released as errata 1.04.8 and the test cases for sequence number handling need a major review based on the Part 4 changes.

TagsNo tags attached.
Files Affected

Relationships

related to 0006034 assignedAlexander Allmendinger Compliance Test Tool (CTT) Unified Architecture Subscription publish Min 02 - retransmission queue 
related to 0005634 closedMatthias Damm 10000-004: Services Subscription publish Min 02 - retransmission queue 
related to 0004795 closedMatthias Damm 10000-004: Services Handling of Publish unclear if retransmission queue is disabled 

Activities

Alexander Allmendinger

2020-10-02 15:43

developer   ~0013010

Updated the expectation for the test case:

Test Case:
Client acknowledges any sequence number that it is not going to ask for retransmission.

Step 1:
Inject a sequenceNumber into the availableSequenceNumbers which has been acknowledged long ago (e.g. Current sequenceNumber=99 | availableSequenceNumber=5).
Expectation: Client acknowledges the injected sequenceNumber and may log the issue.
Step 2:
Inject a sequenceNumber into the availableSequenceNumbers which has been acknowledged shortly ago (e.g. Current sequenceNumber=99 | availableSequenceNumber=97).
Expectation: Client acknowledges the injected sequenceNumber and may log the issue.
Step 3:
Inject a sequenceNumber into the availableSequenceNumbers which is bigger than the current sequenceNumber (e.g. Current sequenceNumber=99 | availableSequenceNumber=101).
Expectation: Client acknowledges the injected sequenceNumber and may log the issue.
Step 4:
Inject a sequenceNumber into the availableSequenceNumbers which is way bigger than the current sequenceNumber (e.g. Current sequenceNumber=99 | availableSequenceNumber=200).
Expectation: Client acknowledges the injected sequenceNumber and may log the issue.

Paul Hunkar

2021-04-01 14:42

administrator   ~0014145

reviewed in CMP call , agreed to changes and closed

Issue History

Date Modified Username Field Change
2020-09-29 07:08 Matthias Damm New Issue
2020-10-02 15:22 Paul Hunkar Relationship added related to 0006034
2020-10-02 15:22 Paul Hunkar Assigned To => Alexander Allmendinger
2020-10-02 15:22 Paul Hunkar Status new => assigned
2020-10-02 15:43 Alexander Allmendinger Status assigned => resolved
2020-10-02 15:43 Alexander Allmendinger Resolution open => fixed
2020-10-02 15:43 Alexander Allmendinger Fixed in Version => 1.04.09.397
2020-10-02 15:43 Alexander Allmendinger Note Added: 0013010
2021-04-01 14:42 Paul Hunkar Status resolved => closed
2021-04-01 14:42 Paul Hunkar Note Added: 0014145
2021-04-01 14:43 Paul Hunkar Relationship added related to 0005634
2021-04-01 14:43 Paul Hunkar Relationship added related to 0004795