Logo etsi

ETSI's Bug Tracker
Main | My View | View Issues | Change Log | Roadmap | Stop monitoring project
  
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 ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007608TDLNew Featurepublic09-02-2017 16:3917-10-2018 13:06
ReporterAndreas Ulrich 
Assigned ToPhilip Makedonski 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusresolvedResolutionfixed 
PlatformOSOS Version
Summary0007608: Advanced test configurations
DescriptionConsider the provision of operations over test configurations:

Configuration use: a TC of name tc2 is used within the TC of name tc1; meaning: all CIs in tc2 and connections between them become accessible in tc1

Component merge: a CI c2 in TC tc2 and a CI c1 in TC tc1 are merged to a single one; the CI c1 will prevail after the merge

Component hide: a CI c can be hidden in a TC tc; meaning: a hidden CI becomes not accessible in the TC and connections from other CIs to this CI are also hidden and not accessible, e.g. in interactions

Renaming of CIs and GIs: the name of a CI from a used TC can be renamed, including the gate instances attached to this CI

Role (re-)assignment of CIs {Tester, SUT}: overwrites an existing assignment

Adding variables to CIs: a new variable is added to a CI (tester or SUT?)


-----------------
Legend:
TC... test configuration
CI... component instance
GI... gate instance
Additional InformationWork was left over from TDL-2 phase. It is recommended to put the topic into the new context of TDL-to-TTCN-3 mapping to ensure a viable solution. Review what operations make most sense in practical applications.
TagsNo tags attached.
Clause Reference(s)8.2.8 Test Configuration
Source (company - Author)    Andreas Ulrich, Siemens AG
Attached Files

- Relationships

-  Notes
(0014574)
Philip Makedonski (manager)
18-04-2017 14:17
edited on: 18-04-2017 14:30

 Some comments regarding the proposed extensions:

Configuration use: a TC of name tc2 is used within the TC of name tc1; meaning: all CIs in tc2 and connections between them become accessible in tc1

[STF522] Plausible. No significant mapping overhead as long as it is only with regard to the configuration specification and not possible to modify during runtime.

Component merge: a CI c2 in TC tc2 and a CI c1 in TC tc1 are merged to a single one; the CI c1 will prevail after the merge

[STF522] Plausible. The meaning of prevail needs to be defined in more detail

Component hide: a CI c can be hidden in a TC tc; meaning: a hidden CI becomes not accessible in the TC and connections from other CIs to this CI are also hidden and not accessible, e.g. in interactions

[STF522] Plausible.

Renaming of CIs and GIs: the name of a CI from a used TC can be renamed, including the gate instances attached to this CI

[STF522] Plausible for CIs, but: benefits are not clear; overhead may be considerable; rejected for GIs, GIs specified at the component type level. Aliasing relevant for tool implementation, may negatively impact understandability of resulting test descriptions.

Role (re-)assignment of CIs {Tester, SUT}: overwrites an existing assignment

[STF522] Plausible, but: will have an impact on the specification of constraints, unless a notion of actual configuration is introduced, which will be computed from the specification

Adding variables to CIs: a new variable is added to a CI (Tester / SUT?)

[STF522] Rejected; variables are defined in component types; this shall not be violated;

[STF522] Overall, for the realisation of the additional features, a notion of "actual" configuration needs to be introduced which is computed from the specification. This will have an impact on the tool implementation and also on the understandability of the specification by users.

[STF522] Furthermore, shall a test configuration TC1 be able to use a test configuration TC2 which already uses a test configuration TC3? Especially, if each one is making some refinements in the way it is using the other configuration it will make it difficult to infer what the actual configuration will be in the end.

[STF522] Ultimately, it may be best to move such features to an extension package as they are non-essential and requiring tool vendors and users to deal with them may add unnecessary overhead.
(0015271)
Philip Makedonski (manager)
17-10-2018 13:06

 Published in ES 203119-7.

- Issue History
Date Modified Username Field Change
09-02-2017 16:39 Andreas Ulrich New Issue
09-02-2017 16:39 Andreas Ulrich Status new => assigned
09-02-2017 16:39 Andreas Ulrich Assigned To => Philip Makedonski
18-04-2017 14:17 Philip Makedonski Note Added: 0014574
18-04-2017 14:19 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:23 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:23 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:24 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:24 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:25 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:27 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:28 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:28 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:29 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:29 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:29 Philip Makedonski Note Edited: 0014574 View Revisions
18-04-2017 14:30 Philip Makedonski Note Edited: 0014574 View Revisions
17-10-2018 13:06 Philip Makedonski Note Added: 0015271
17-10-2018 13:06 Philip Makedonski Status assigned => resolved
17-10-2018 13:06 Philip Makedonski Resolution open => fixed

MantisBT 1.2.14 [^]
Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker