| |
ETSI's Bug Tracker |
| Anonymous | Login | Signup for local Mantis account | 21-05-2024 00:56 IST |  |
| Main | My View | View Issues | Change Log | Roadmap | Stop monitoring project |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
| 0007887 | TDL | New Feature | public | 05-12-2019 11:03 | 13-04-2021 09:38 | ||||||||
| Reporter | Finn Kristoffersen | ||||||||||||
| Assigned To | Finn Kristoffersen | ||||||||||||
| Priority | normal | Severity | feature | Reproducibility | have not tried | ||||||||
| Status | assigned | Resolution | open | ||||||||||
| Platform | OS | OS Version | |||||||||||
| Summary | 0007887: New feature to allow for alternative values in parameter bindings in TDL Test Objectives | ||||||||||||
| Description | In TDL test objectives (TO) a parameter binding can specifify only a single specific value or (any or omitted value). However, in certain cases the requirement is such that a set of specific values is allowed. With current TDL TO syntax this is not possible. The syntax shall be modified to allow for a list of alternative values to be defined in a parameter binding | ||||||||||||
| Additional Information | In TDL Test Objective standard v.1.3.1 the parameter binding production rule is defined as: ParameterBinding ::= Identifier AssignmentQualifier { Qualifier } StaticDataUse ; The latter part should be extended to allow for a list of values, e.g.: .. . StaticDataUse { 'or' StaticDataUse } ; | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Clause Reference(s) | 203 119-4 v.1.3.1 Annex B.2 | ||||||||||||
| Source (company - Author) | Finn Kristoffersen | ||||||||||||
| Attached Files |  TDL_TO_ParameterBinding.docx [^] (14,800 bytes) 05-12-2019 11:03 | ||||||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0015916) Philip Makedonski (manager) 12-04-2021 14:50 |
After looking at the example, the required changes will likely reach beyond what is proposed if the compatibility with predefined data is to be maintained. The semantic implications of using "or" for Members, for example, needs to be clarified. Also whether "one or more" shall be interpreted as a collection, with a minimum number of elements... Data constraints may help in this regard. |
|
(0015917) Philip Makedonski (manager) 12-04-2021 14:56 |
Regarding "one or more", it appears to be more like a "pattern" for the elements in the collection rather than the list of items in the collection (as currently indicated in TDL Part 1) |
|
(0015918) Philip Makedonski (manager) 13-04-2021 09:38 |
Alternative member and assignment options could be expressed with variants as well, in the end an implementation of a test will have to determine what is to be expected, and especially also what is to be sent. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 05-12-2019 11:03 | Finn Kristoffersen | New Issue | |
| 05-12-2019 11:03 | Finn Kristoffersen | Status | new => assigned |
| 05-12-2019 11:03 | Finn Kristoffersen | Assigned To | => Finn Kristoffersen |
| 05-12-2019 11:03 | Finn Kristoffersen | File Added: TDL_TO_ParameterBinding.docx | |
| 12-04-2021 14:50 | Philip Makedonski | Note Added: 0015916 | |
| 12-04-2021 14:56 | Philip Makedonski | Note Added: 0015917 | |
| 13-04-2021 09:38 | Philip Makedonski | Note Added: 0015918 | |
|
Issue History |
| MantisBT 1.2.14 [^] Copyright © 2000 - 2024 MantisBT Team |
 |