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

ID | Project | Category | View Status | Date Submitted | Last Update
0000422 | Part 01: TTCN-3 Core Language | New Feature | public | 24-11-2006 14:46 | 15-07-2008 11:44

Reporter | Stephan Schulz |
Assigned To | Jens Grabowski |
Priority | normal | Severity | feature | Reproducibility | N/A
Status | closed | Resolution | won't fix |
Platform |  | OS |  | OS Version |
Product Version | v3.1.1 (published 2005-06) |
Target Version | v4.1.1 (published 2009-06) | Fixed in Version |  |
Clause Reference(s) | 14.1.1
Source (company - Author) | Siemens

Summary | 0000422: sending templates with unassigned values via internal (connected) ports

Description

For the send operation, the template shall be fully defined, i.e. all fields shall resolve to actual values. But for some reason, templates must be exchanged between different test components within the test system. Currently it is only allowed to use templates as parameters of a function, which could be used to start the behavior of a PTC. But there is no mechanism that allows the exchange of templates during runtime of the PTCs. We should allow send templates with undefined fields only for internal (connected) ports. For templates sent to SUT (mapped) ports, the template should remain fully defined.
At the time of the send operation, the template shall be fully defined i.e. all fields shall resolve to actual values and no matching mechanisms shall be used in the template fields, neither directly nor indirectly. (14.1.1)

Steps To Reproduce |
Additional Information | Proposed Solution: It should be allowed that the a send template can contain matching values (*, ?, value lists, ranges, etc.) for internal (connected) ports. Matching rules to match matching values must be defined, e.g always use ? to match a matching value or * if the associated field is opional.
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
24-11-2006 14:46 | Stephan Schulz | New Issue |
24-11-2006 14:46 | Stephan Schulz | Clause Reference(s) | => 14.1.1
24-11-2006 14:46 | Stephan Schulz | Source (company - Author) | => Siemens
24-11-2006 14:47 | Stephan Schulz | Note Added: 0000322 |
24-11-2006 14:47 | Stephan Schulz | Status | new => feedback
24-11-2006 15:02 | Stephan Schulz | Note Added: 0000329 |
15-06-2007 19:14 | Stephan Schulz | Status | feedback => assigned
15-06-2007 19:14 | Stephan Schulz | Assigned To | => Ina Schieferdecker
13-10-2007 19:24 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Jens Grabowski
18-10-2007 13:11 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
15-07-2008 11:43 | Ina Schieferdecker | Note Added: 0006274 |
15-07-2008 11:44 | Ina Schieferdecker | Status | assigned => closed
15-07-2008 11:44 | Ina Schieferdecker | Resolution | open => won't fix

Notes

(0000322)
Stephan Schulz
24-11-2006 14:47

Waiting for providers response

(0000329)
Stephan Schulz
24-11-2006 15:02

We are expecting a more detailed description of the consequences, especially at the language level

(0006274)
Ina Schieferdecker
15-07-2008 11:43

could be done, but adds complexity to TTCN-3 which seems to be unneccessary as template passing could also be done via template parameters to test component functions