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

ID | Project | Category | View Status | Date Submitted | Last Update
0007196 | Part 01: TTCN-3 Core Language | Clarification | public | 09-10-2015 15:55 | 05-01-2016 15:41

Reporter | Jacob Wieland - Spirent |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.8.1 (published 2016-07) | Fixed in Version | v4.8.1 (published 2016-07) |
Clause Reference(s) | 21.3.2
Source (company - Author) | Testing Technologies - Jacob Wieland

Summary | 0007196: start operation with altstep should be allowed
Description | There is really no need to restrict the start operation to only apply to functions and not to altsteps. Altsteps in this context are just special functions containing only an alt-statement (and maybe some variable declarations). As long as the runs on and other compatibilities are adhered to, there is no need for this restriction.
Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR7196_resolution_v1.docx (454,526) 05-11-2015 09:48 http://oldforge.etsi.org/mantis/file_download.php?file_id=3366&type=bug CR7196_resolution_v2.docx (1,674,920) 05-11-2015 15:35 http://oldforge.etsi.org/mantis/file_download.php?file_id=3369&type=bug

Issue History
Date Modified | Username | Field | Change
09-10-2015 15:55 | Jacob Wieland - Spirent | New Issue |
03-11-2015 16:11 | Gyorgy Rethy | Note Added: 0013479 |
03-11-2015 16:11 | Gyorgy Rethy | Assigned To | => Jacob Wieland - Spirent
03-11-2015 16:11 | Gyorgy Rethy | Status | new => assigned
04-11-2015 13:58 | Gyorgy Rethy | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
04-11-2015 13:59 | Gyorgy Rethy | Target Version | => v4.8.1 (published 2016-07)
05-11-2015 09:48 | Jacob Wieland - Spirent | File Added: CR7196_resolution_v1.docx |
05-11-2015 09:49 | Jacob Wieland - Spirent | Note Added: 0013498 |
05-11-2015 09:49 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Jens Grabowski
05-11-2015 09:49 | Jacob Wieland - Spirent | Status | assigned => confirmed
05-11-2015 13:48 | Jens Grabowski | Note Added: 0013499 |
05-11-2015 13:48 | Jens Grabowski | Status | confirmed => assigned
05-11-2015 13:48 | Jens Grabowski | Assigned To | Jens Grabowski => Jacob Wieland - Spirent
05-11-2015 15:35 | Jacob Wieland - Spirent | File Added: CR7196_resolution_v2.docx |
05-11-2015 15:43 | Jacob Wieland - Spirent | Note Added: 0013507 |
05-11-2015 15:43 | Jacob Wieland - Spirent | Note Added: 0013508 |
05-11-2015 15:43 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Jens Grabowski
05-11-2015 15:43 | Jacob Wieland - Spirent | Status | assigned => confirmed
28-12-2015 10:29 | Jens Grabowski | Assigned To | Jens Grabowski => Gyorgy Rethy
28-12-2015 10:29 | Jens Grabowski | Status | confirmed => resolved
05-01-2016 15:41 | Gyorgy Rethy | Note Added: 0013660 |
05-01-2016 15:41 | Gyorgy Rethy | Status | resolved => closed
05-01-2016 15:41 | Gyorgy Rethy | Resolution | open => fixed
05-01-2016 15:41 | Gyorgy Rethy | Fixed in Version | => v4.8.1 (published 2016-07)

Notes

(0013479)
Gyorgy Rethy
03-11-2015 16:11

STF discussion: basically agreed. Prepare text proosal.

(0013498)
Jacob Wieland - Spirent
05-11-2015 09:49

please review and resolve

(0013499)
Jens Grabowski
05-11-2015 13:48

Sorry, but I assign it back due to the following reasons: - the term behaviour as shorthand for functions and altsteps is nowhere defined (test cases also define behaviour) - in the function section it is explicitly mentioned that functions started with a start test component operation shall always have a runs on clause. Maybe we have to discuss these issues.

(0013507)
Jacob Wieland - Spirent
05-11-2015 15:43

There was already a definition of test behaviour (or behaviour) in the definitions section that referred to testcases, functions and altsteps (but excluded altsteps directly started for ptcs, of course). I have included another definition "behaviour definition" which enumerates the different kinds of behaviour definitions explicitly. If the proposed text remains unclear, maybe this terminus could be used in certain places.
the term behaviour is widely used through the whole standard (and sometimes with additions like function behaviour, behaviour function, etc), but mostly as a running sequence of statements and most of the cases refer to these 3 entities (though control part, of course, should also be considered as behaviour, though maybe not test behaviour). Especially in section 21.3 it is often used to describe any behaviour running on a component.
I have tried to make the use of the terms more consistent through the standard and to include altstep in any place that was missing that was previously only mentioning functions.
I have also added the same restriction for started altsteps as for started functions.

(0013508)
Jacob Wieland - Spirent
05-11-2015 15:43

please review again

(0013660)
Gyorgy Rethy
05-01-2016 15:41

Added to draft V4.7.5