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

ID | Project | Category | View Status | Date Submitted | Last Update
0003843 | Part 01: TTCN-3 Core Language | New Feature | public | 24-07-2008 08:45 | 09-12-2008 10:22

Reporter | wangguolong |
Assigned To | Thomas DeiÃŸ |
Priority | normal | Severity | feature | Reproducibility | always
Status | closed | Resolution | won't fix |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.1.1 (published 2009-06) | Fixed in Version |  |
Clause Reference(s) | NA
Source (company - Author) |

Summary | 0003843: Support C++ like Exception Handling mechanism

Description

It is proposed to add one new features to the TTCN-3 core language standard that C++ like exception handling mechanism is supported in core language. Sometimes the errors in different level can be handled using scripts by users flexibly. This is realized and proved useful in real testing.
Here is the example:
try
{
[block statment]
}
catch
{
[block statment]
var charstring e:= "exception A";
throw (e);
}

Steps To Reproduce |

Additional Information

1. try...catch... statment only catches the exception which caused by executor or internal error. The user defined exception is not supported and transferred.
2. try...catch gives the control of the execution of test suites to the users when internal runtime error happens. Most times users did not want to terminate the automatic execution even if the runtime error happened. This statment gives them the way.

Tags | No tags attached.

Relationships

related to | 0002565 | closed | Ina Schieferdecker | Part 06: TTCN-3 Control Interface | TTCN-3 Exceptions

Attached Files | TTCN-3_exceptions_02.ppt (206,848) 14-08-2008 12:34 http://oldforge.etsi.org/mantis/file_download.php?file_id=1599&type=bug

Issue History
Date Modified | Username | Field | Change
24-07-2008 08:45 | wangguolong | New Issue |
24-07-2008 08:45 | wangguolong | Status | new => assigned
24-07-2008 08:45 | wangguolong | Assigned To | => Ina Schieferdecker
24-07-2008 08:45 | wangguolong | Clause Reference(s) | => NA
24-07-2008 08:45 | wangguolong | Source (company - Author) | =>
11-08-2008 10:35 | Thomas DeiÃŸ | Relationship added | related to 0002565
11-08-2008 10:35 | Thomas DeiÃŸ | Assigned To | Ina Schieferdecker => Thomas DeiÃŸ
11-08-2008 10:53 | Thomas DeiÃŸ | Note Added: 0006482 |
14-08-2008 12:34 | Thomas DeiÃŸ | File Added: TTCN-3_exceptions_02.ppt |
17-08-2008 09:10 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
09-12-2008 10:21 | Ina Schieferdecker | Note Added: 0007588 |
09-12-2008 10:22 | Ina Schieferdecker | Status | assigned => closed
09-12-2008 10:22 | Ina Schieferdecker | Resolution | open => won't fix

Notes

(0006482)
Thomas DeiÃŸ
11-08-2008 10:53

Regarding CR 2565: The setverdict statement has been extended already such that a reason or cause for the verdict can be provided by the user. CR2565 will provide the corresponding extensions for the TRI such that the reason can also be passed to the TCI-TM.
So far, STF 349 considers that user-defined exceptions do not extend the expressiveness of the language. Surely, some cases can be written in a more simple way. Would it be possible to get some more examples or use cases showing the benefit of introducing user-defined exceptions. (you can contact me directly at thomas.deiss@nsn.com).
Catching runtime system errors and continueing test case execution would to some extend break the philosophy of TTCN-3. Once something went wrong in the test case - causing a runtime system error - the verdict would have been set to 'error' and further execution of the test case was considered meaningless. When catching runtime errors as exceptions, the verdict should not be set to 'error'.
These are some initial thoughts by STF 349 on the CR. A more detailed analysis will be done.

(0007588)
Ina Schieferdecker
09-12-2008 10:21

For time being, the Maintenance STF decided not to introduce C++ like exceptions into TTCN-3. See also CR2565.