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

ID | Project | Category | View Status | Date Submitted | Last Update
0006239 | Part 01: TTCN-3 Core Language | Technical | public | 01-08-2012 09:56 | 05-01-2015 18:25

Reporter | Tomas Urban |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.4.1 (published 2012-04) |
Target Version | v4.7.1 (published 2015-06) | Fixed in Version | v4.7.1 (published 2015-06) |
Clause Reference(s) | 24
Source (company - Author) | Elvior

Summary | 0006239: Restriction on verdict operation
Description | Both verdict operations (setverdict, getverdict) should contain similar restriction as the testcase.stop operation regarding invocation from the module control part: The setverdict/getverdict operation shall not be used in the module control part or functions invoked directly or indirectly by the module control part.
Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |

Attached Files

Another TTCN-3 language question from ETSI STF446.htm (14,825) 11-12-2012 14:04
http://oldforge.etsi.org/mantis/file_download.php?file_id=2764&type=bug
CR6239-Resolution-JG-130828.doc (851,968) 28-08-2013 10:50
http://oldforge.etsi.org/mantis/file_download.php?file_id=2866&type=bug
CR6239-Resolution-JG-130828-V2.doc (851,968) 28-08-2013 15:57
http://oldforge.etsi.org/mantis/file_download.php?file_id=2872&type=bug
CR6239-Resolution-JW.doc (853,504) 07-10-2013 13:14
http://oldforge.etsi.org/mantis/file_download.php?file_id=2889&type=bug
CR6239-Resolution-JW-IS.doc (854,016) 11-10-2013 16:22
http://oldforge.etsi.org/mantis/file_download.php?file_id=2933&type=bug
CR6239-Resolution-v5.doc (845,824) 07-10-2014 11:06
http://oldforge.etsi.org/mantis/file_download.php?file_id=3093&type=bug

Issue History
Date Modified | Username | Field | Change
01-08-2012 09:56 | Tomas Urban | New Issue |
01-08-2012 09:56 | Tomas Urban | Clause Reference(s) | => 24
01-08-2012 09:56 | Tomas Urban | Source (company - Author) | => Elvior
07-08-2012 19:01 | Gyorgy Rethy | Status | new => assigned
07-08-2012 19:01 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
07-08-2012 19:17 | Gyorgy Rethy | Note Added: 0010989 |
07-08-2012 19:18 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Tomas Urban
08-08-2012 10:38 | Gyorgy Rethy | Note Added: 0010994 |
08-08-2012 10:39 | Gyorgy Rethy | Note Edited: 0010994 |
08-08-2012 10:39 | Gyorgy Rethy | Assigned To | Tomas Urban => Gyorgy Rethy
10-12-2012 16:57 | Gyorgy Rethy | Target Version | => Edition 4.5.1
11-12-2012 13:57 | Gyorgy Rethy | Note Added: 0011222 |
11-12-2012 14:00 | Gyorgy Rethy | Note Edited: 0011222 |
11-12-2012 14:04 | Gyorgy Rethy | File Added: Another TTCN-3 language question from ETSI STF446.htm |
13-12-2012 14:14 | Gyorgy Rethy | Note Added: 0011254 |
13-12-2012 14:55 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Jens Grabowski
14-05-2013 15:21 | Gyorgy Rethy | Target Version | Edition 4.5.1 => v4.7.1 (published 2015-06)
12-07-2013 10:53 | Jens Grabowski | Note Added: 0011571 |
27-08-2013 11:09 | Jens Grabowski | Note Added: 0011608 |
28-08-2013 10:49 | Jens Grabowski | Note Added: 0011619 |
28-08-2013 10:50 | Jens Grabowski | File Added: CR6239-Resolution-JG-130828.doc |
28-08-2013 10:51 | Jens Grabowski | Note Added: 0011620 |
28-08-2013 10:51 | Jens Grabowski | Assigned To | Jens Grabowski => Jacob Wieland - Spirent
28-08-2013 11:23 | Jacob Wieland - Spirent | Note Added: 0011622 |
28-08-2013 11:23 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Jens Grabowski
28-08-2013 11:23 | Jacob Wieland - Spirent | Status | assigned => confirmed
28-08-2013 15:57 | Jens Grabowski | File Added: CR6239-Resolution-JG-130828-V2.doc |
28-08-2013 15:58 | Jens Grabowski | Note Added: 0011629 |
28-08-2013 15:59 | Jens Grabowski | Status | confirmed => assigned
28-08-2013 15:59 | Jens Grabowski | Assigned To | Jens Grabowski => Gyorgy Rethy
30-08-2013 09:44 | Gyorgy Rethy | Status | assigned => confirmed
30-08-2013 10:08 | Gyorgy Rethy | Note Added: 0011650 |
30-08-2013 10:08 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Jacob Wieland - Spirent
30-08-2013 10:08 | Gyorgy Rethy | Status | confirmed => assigned
07-10-2013 13:14 | Jacob Wieland - Spirent | File Added: CR6239-Resolution-JW.doc |
07-10-2013 13:17 | Jacob Wieland - Spirent | Note Added: 0011684 |
07-10-2013 13:17 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Gyorgy Rethy
07-10-2013 13:17 | Jacob Wieland - Spirent | Status | assigned => confirmed
07-10-2013 16:21 | Gyorgy Rethy | Note Added: 0011691 |
07-10-2013 16:21 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Ina Schieferdecker
07-10-2013 16:21 | Gyorgy Rethy | Status | confirmed => resolved
07-10-2013 16:21 | Gyorgy Rethy | Resolution | open => fixed
11-10-2013 16:21 | Ina Schieferdecker | Note Added: 0011790 |
11-10-2013 16:22 | Ina Schieferdecker | File Added: CR6239-Resolution-JW-IS.doc |
11-10-2013 16:22 | Ina Schieferdecker | Status | resolved => assigned
11-10-2013 16:22 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Gyorgy Rethy
29-11-2013 14:15 | Jacob Wieland - Spirent | Note Added: 0011880 |
08-04-2014 16:50 | Gyorgy Rethy | Target Version | v4.6.1 (published 2014-06) => v4.7.1 (published 2015-06)
19-06-2014 17:22 | Gyorgy Rethy | Category | Editorial => Technical
06-10-2014 14:13 | Gyorgy Rethy | Note Added: 0012231 |
06-10-2014 14:13 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Tomas Urban
07-10-2014 11:06 | Tomas Urban | File Added: CR6239-Resolution-v5.doc |
07-10-2014 11:10 | Tomas Urban | Note Added: 0012250 |
07-10-2014 11:10 | Tomas Urban | Status | assigned => resolved
07-10-2014 11:10 | Tomas Urban | Assigned To | Tomas Urban => Jens Grabowski
07-10-2014 11:11 | Tomas Urban | Status | resolved => feedback
07-10-2014 11:11 | Tomas Urban | Resolution | fixed => reopened
07-10-2014 11:11 | Tomas Urban | Status | feedback => confirmed
07-10-2014 11:11 | Tomas Urban | Resolution | reopened => open
07-10-2014 14:47 | Jens Grabowski | Note Added: 0012255 |
07-10-2014 14:47 | Jens Grabowski | Assigned To | Jens Grabowski => Gyorgy Rethy
07-10-2014 14:47 | Jens Grabowski | Status | confirmed => assigned
07-10-2014 14:47 | Jens Grabowski | Status | assigned => resolved
07-10-2014 14:47 | Jens Grabowski | Resolution | open => fixed
05-01-2015 18:25 | Gyorgy Rethy | Note Added: 0012628 |
05-01-2015 18:25 | Gyorgy Rethy | Status | resolved => closed
05-01-2015 18:25 | Gyorgy Rethy | Fixed in Version | => v4.7.1 (published 2015-06)

Notes

(0010989)
Gyorgy Rethy
07-08-2012 19:17

In general, table 16 specifies which operation can be used where. In addition, table 31 defines what can be used in the control part.
I rather propose to remove the restriction from the text of clause 21.2.1 and other similar places in the standard ( 1st paragraph of clauses 19, 19.7, 1st paragraph of the semantic description of clause 19.8), where we are mentioning what can be used in the control part.

(0010994)
Gyorgy Rethy
08-08-2012 10:38 (edited on: 08-08-2012 10:39)

STF discussion 2012-08-08: it is not clearly defined in the standard what "use" means: the given operation shall not occur at a given place in the code or it shall not be executed runtime. Users (tool vendors) and 3GPP shall be asked. Invoking functions from control, specific places (guards, etc.) are affected.

(0011222)
Gyorgy Rethy
11-12-2012 13:57 (edited on: 11-12-2012 14:00)

E-mail has been sent to TTCN-3 tool vendors on 10-Aug and re-sent on 11-Dec. Response received from STF 160 only.

(0011254)
Gyorgy Rethy
13-12-2012 14:14

STF discussion 2012-12-13: the runtime usaga of testcase.stop shall be forbidden *option (2) from the mail sent to vendors. To do:
- add a definition of the term "use" to the definitions section
- if that is agreed, check all places where "use" is used and change if needed. it is agreed earlier today, that constants and non-parameterized global templates shall be initialized just once, at declaration.

(0011571)
Jens Grabowski
12-07-2013 10:53

A restriction similar to "The test case stop operation shall not be used in the module control part or functions invoked directly or indirectly by the module control part." only appears in the restrictions paragraph of "testcase.stop". According to GyÃ¶rgy's proposal, this restriction should be deleted from 21.2.1.

(0011608)
Jens Grabowski
27-08-2013 11:09

It is not possible to provide a unique and unambiguous definition of the term "use" in the TTCN-3 standard.
Only Part I includes round about appearences of "use" or "used".
The term "use" in combination with a TTCN-3 statement is mainly used (I cannot even here avoid this word) in the following manners:
(1) "use" refers to specification, e.g., TTCN-3 statement X "can be used in test cases, functions, ...."
(2) "use" refers to execution, e.g., "Configuration operations are used to set up and control test components."
(3) "use" may be replaced by "applied to", e.g., "The stop operation is used to stop a running timer."
(4) the general term "use" refers to a mixture of (1), (2) and (3).
My conclusion is that we should not provide a definition for the term "use", but always provide clarifications whenever an ambiguity is detected. Ambiguities should be reported as CRs as ususal.

(0011619)
Jens Grabowski
28-08-2013 10:49

CR implemented as discussed by the STF on 27.08.2013.
- Column headings of table 15 have been changed to highlight an "execution" use instead of a "specification" use. E.g., testcase.stop may occur in a function which is indirectly called by module control. The occurence itself shall not automatically cause an error.
- In all restriction paragraphs of statements/operations mentioned in table 15, a reference to table 15 has been added.
- no definition of the term "use" is provided (see my Note from 27.8.2013)

(0011620)
Jens Grabowski
28-08-2013 10:51

Assigned for proofchecking to Jacob.

(0011622)
Jacob Wieland - Spirent
28-08-2013 11:23

The third column should rather be headed by: Can be called in a testing context by functions called from templates, boolean guards, alternative event parts and initialization of altstep local definitions. I.e., the events-parts are missing. Shouldn't we also make the disjointness of the columns more explicit?

(0011629)
Jens Grabowski
28-08-2013 15:58

Table column heading changed according to Jacob's suggestion. Assigned to GyÃ¶rgy for final proofchecking.

(0011650)
Gyorgy Rethy
30-08-2013 10:08

In general OK with me but two comments:
- I don't understand what "alternative event parts" means :-/? No such term is defined or used in the standard. If the content of the bracket following a receiving statement is meant here, this is called "Matching part" in clause 22.1.4.2. But in this case a clause reference should be given in a note.
- In table 15, NOTE-s should be just numbered list items like:
(1) ....
(2) ....

(0011684)
Jacob Wieland - Spirent
07-10-2013 13:17

changed alternative event part to receive part of receive operation, timeout, done or killed operation which summarizes all existing event possibilities (receive part is also described in the receive operations overview)

(0011691)
Gyorgy Rethy
07-10-2013 16:21

Fine with me. Tomas, if possible, pls. check it as well.

(0011790)
Ina Schieferdecker
11-10-2013 16:21

The proposed rewording of the columns of table 15 is confusing as testing context is nowhere else defined and used in second last and last column with different meanings. Hence, another proposal is attached. The other changes are fine for me.

(0011880)
Jacob Wieland - Spirent
29-11-2013 14:15

the meanings of testing context in the columns was exactly the same: directly or indirectly invoked from a testcase

(0012231)
Gyorgy Rethy
06-10-2014 14:13

Pls. final check if the wording in the table headers are OK or need some adjustment.

(0012250)
Tomas Urban
07-10-2014 11:10

After a discussion, I changed the header of the last column in the table 15 to "Can be directly or indirectly invoked from specific places". This is much shorter than the previous description and the term is well described in the clause 16.1.4. The rest of the proposal is fine by me. Jens, could you please check if the change is acceptable and in case it is mark the CR as resolved?

(0012255)
Jens Grabowski
07-10-2014 14:47

Resolution is also fine with me.

(0012628)
Gyorgy Rethy
05-01-2015 18:25

Added to draft V4.6.3