ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0007890 | Part 01: TTCN-3 Core Language | New Feature | public | 11-12-2019 11:45 | 14-08-2020 11:41

Reporter | Jacob Wieland - Spirent |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | won't fix |
Platform |  | OS |  | OS Version |
Product Version | 4.11.1 (published 2019-05) |
Target Version |  | Fixed in Version |  |
Clause Reference(s) | 8.2.1
Source (company - Author) | Spirent - Jacob Wieland

Summary | 0007890: module parameters should behave like variables during control part execution

Description

Module parameters are supposed to be constant during a testcase execution.
However, test management that allows the execution of multiple testcases allows changing module parameters between the exeuction of testcases.
Maybe it could be allowed to treat module parameters as variables during the control execution so that the control part can assign new values before execution.
An additional benefit of this comes into play in the following scenario.
A library providing module parameters doesn't provide default values because it can be used in very different contexts so that no default parameter binding can be established. Thus, it would be beneficial if you could declare these parameters without defaults and in the different scenarios define initialization-control parts that fill the module parameters context-sensitive with proper defaults.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
11-12-2019 11:45 | Jacob Wieland - Spirent | New Issue |
12-12-2019 12:50 | KristÃ³f Szabados | Note Added: 0015508 |
13-12-2019 10:07 | Jacob Wieland - Spirent | Note Added: 0015510 |
16-12-2019 08:56 | Jens Grabowski | Note Added: 0015511 |
16-12-2019 08:57 | Jens Grabowski | Assigned To | => Jens Grabowski
16-12-2019 08:57 | Jens Grabowski | Status | new => assigned
14-08-2020 11:41 | Jens Grabowski | Note Added: 0015750 |
14-08-2020 11:41 | Jens Grabowski | Status | assigned => closed
14-08-2020 11:41 | Jens Grabowski | Assigned To | Jens Grabowski => Gyorgy Rethy
14-08-2020 11:41 | Jens Grabowski | Resolution | open => won't fix

Notes

(0015508)
KristÃ³f Szabados
12-12-2019 12:50

For me module parameters were always about parameterising modules not testcases. So I would prefer to have module parameters behave as contants in the control part.

(0015510)
Jacob Wieland - Spirent
13-12-2019 10:07

What is the parameterization of modules for, though if not for usage inside testcases? We also want to parameterize the modules, but the parameterization should be possible to change between testcases, or at least, be flexible BEFORE the start of testcases.
So, at least the initialization of module parameters inside the control part (especially those that have no default value) should be possible. That would already help immensely as then different control parts could initialize the module parameters differently before the start of testcases.

(0015511)
Jens Grabowski
16-12-2019 08:56

STF discussion: There are pros and cons for this proposal. The feature may be a candidate for the configuration and deployment package. To be revisited in 2020.

(0015750)
Jens Grabowski
14-08-2020 11:41

STF will not continue discussions on this CR.