Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

ID

Project

Category

View Status

Date Submitted

Last Update

0008013

TDL

Technical

public

06-03-2021 08:02

22-04-2021 17:13

Reporter

schauppk

Assigned To

Priority

normal

Severity

major

Reproducibility

have not tried

Status

new

Resolution

open

Platform

OS

OS Version

Summary

0008013: Extend workflow to allow feedback from execution to level to specification level

Description

In contrast to some user oriented documentations e.g. TDL-Booth-UCAAT-2019.pdf the workflow for design and verification of test specifications is not a straight forward but an iterative development process and requires feed back from execution phase into the specification level e.g. unforeseen but valid events received at the testers end. Such events could include quite complex message details and the tooling should provide means to easily enrich the expected flow of messages. Additionally it would be good practice to present the results of a test run to the user in the same representation as used for designing the test specification and definition of expected results.

Additional Information

Some remarks for the case of traditional protocol test using encoded message exchange: The “Lowest common denominator” for representation of message contents is the encoded bitstring in hexadecimal representation. Assuming the tooling is aware of the protocol definition – see MANTIS TDL 0008011 – during decoding of the binary string we dynamically could setup a hierarchical object tree representing the message content. Such structure may be used for comparison of expected and received results as well as for an import of message flows from log files in textual representation.

Tags

No tags attached.

Clause Reference(s)

TDL Workflow Definition

Source (company - Author)

adare GmbH - Konrad Schaupp

Relationships

Notes
(0015921) Philip Makedonski (manager) 14-04-2021 14:52	Possible contributions could include refinement of Clause 4.3 to include also the use case of importing / analysing test execution logs, e.g. represented in Figure 4.2, where test logs can be used for refinement of TDs or for comparison between specified and actual behaviour. If there is any concrete guidelines on how to achieve that, they can be brought initially under TR 103 119. Further details and elaboration appreciated.

(0015922) Philip Makedonski (manager) 14-04-2021 14:54	Tooling aspects are out of scope. Specific interpretation and importing of execution logs are tool- (and possibly protocol) dependent.

(0015923) Philip Makedonski (manager) 14-04-2021 14:55	Encoded hexstring is one of the common formats for importing logs.

(0015927) schauppk (reporter) 22-04-2021 17:13	This CR highly relates, infact it depends on, 0008011: Make TDL aware of “protocol definitions” to be used in TOs and TDs. With CR 8011 implemented one could establish a common basis for all steps in the test specification and execution process, as all "talk about the same thing" as defined in the common protocol description(s).

Issue History
Date Modified	Username	Field	Change
06-03-2021 08:02	schauppk	New Issue
14-04-2021 14:52	Philip Makedonski	Note Added: 0015921
14-04-2021 14:54	Philip Makedonski	Note Added: 0015922
14-04-2021 14:55	Philip Makedonski	Note Added: 0015923
22-04-2021 17:13	schauppk	Note Added: 0015927

MantisBT 1.2.14 [^]

Copyright © 2000 - 2024 MantisBT Team