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

ID | Project | Category | View Status | Date Submitted | Last Update
0000413 | Part 01: TTCN-3 Core Language | New Feature | public | 24-11-2006 14:29 | 16-02-2010 14:36

Reporter | Stephan Schulz |
Assigned To | Jens Grabowski |
Priority | high | Severity | feature | Reproducibility | N/A
Status | closed | Resolution | fixed |
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) | TBD
Source (company - Author) | dr. György Réthy, Ericsson

Summary | 0000413: Static test configurations

Description

Though TTCN-3 has been designed for automatic test execution, this is far not the only use of TTCN-3 in practice. The typical workflow is, that TTCN-3 test cases are developed for basic or function testing purposes, used (validated) in an interactive (semi-manual) way in the first test campaign and re-used later in automated regression testing. For the success of TTCN-3 it is essential to features to the language to support also interactive test execution. In this mode testers are executing test cases one-by-one or smaller groups and selects the next test to be elaborated depending on the result (determined by log analysis) of the executed one. Very often test cases are executed in different combinations and order and the SUT behaviour even monitored during test case execution.
When executing TTCN-3 tests in real test environments (not only in interactive mode), in many cases it would be very important not to destroy the test configurations at the end of a test case. There are several reasons for that:
- By destroying the test configuration all data collected during T execution is lost. At the beginning of the next test case there is no information about the SUT's status, user data (e.g. call/session references, SUT-assigned IDs etc.). Today this problem is solved by saving the data on disk at the end of each test case and re-loading it at the beginning of the next test case. This complicates the TTCN-3 code significantly (collecting data from all PTCs, saving it, then reading the data and distribute to new PTCs) and in case of test case errors all data received from the SUT during the given test case is lost.
- In practice it is impossible to start test cases from a null state. The whole configuration of the SUT and other tools used for execution may take as long as 1/2 hour that can not be allowed for every test case. The actual status of the SUT may not be known without having this information from previous test cases.
- SUTs often require keep-alive signals to avoid maintenance alarms or blocking signalling links. This requires keep-alive timers running and sending/receiving keep-alive signals between test cases. TTCN-3 is unable to provide this functionality today.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.

Relationships

related to | 0004275 | closed | Ina Schieferdecker | New Concepts to be defined via Packages
related to | 0000381 | closed | Jens Grabowski | External Applications
related to | 0002143 | closed | Jens Grabowski | Invoke test cases from/on test components
related to | 0002758 | closed | Jens Grabowski | Queueing of function calls

Attached Files

CR_408 Static test configurations.doc (58,368) 24-11-2006 14:29
http://oldforge.etsi.org/mantis/file_download.php?file_id=41&type=bug
CR-0413-Static-Test-Configurations.ppt (109,568) 12-08-2008 16:28
http://oldforge.etsi.org/mantis/file_download.php?file_id=1588&type=bug
es_TTCN3PackageTemplate_Configuration-V1_JG_TD.doc (220,160) 13-01-2009 11:41
http://oldforge.etsi.org/mantis/file_download.php?file_id=1951&type=bug
es_TTCN3PackageTemplate_Configuration-V2-090115.doc (251,392) 15-01-2009 17:16
http://oldforge.etsi.org/mantis/file_download.php?file_id=1958&type=bug
TRI and TCI for DeplConfig.ppt (62,976) 21-04-2009 11:58
http://oldforge.etsi.org/mantis/file_download.php?file_id=2094&type=bug
TRI and TCI for DeplConfig_v2.ppt (61,952) 21-04-2009 18:18
http://oldforge.etsi.org/mantis/file_download.php?file_id=2101&type=bug
es202781_DeploymentConfiguration_220409.doc (588,288) 23-04-2009 14:41
http://oldforge.etsi.org/mantis/file_download.php?file_id=2114&type=bug
Deployment-Semantics-100120.doc (1,599,488) 21-01-2010 15:31
http://oldforge.etsi.org/mantis/file_download.php?file_id=2325&type=bug
es202781_DeploymentConfiguration-100121-complete.zip (674,924) 21-01-2010 17:10
http://oldforge.etsi.org/mantis/file_download.php?file_id=2326&type=bug
es202781_DeploymentConfiguration-100122-complete.zip (675,686) 22-01-2010 10:30
http://oldforge.etsi.org/mantis/file_download.php?file_id=2327&type=bug

Issue History
Date Modified | Username | Field | Change
24-11-2006 14:29 | Stephan Schulz | New Issue |
24-11-2006 14:29 | Stephan Schulz | File Added: CR_408 Static test configurations.doc |
24-11-2006 14:29 | Stephan Schulz | Clause Reference(s) | => TBD
24-11-2006 14:29 | Stephan Schulz | Source (company - Author) | => dr. György Réthy, Ericsson
15-06-2007 19:16 | Stephan Schulz | Status | new => assigned
15-06-2007 19:16 | Stephan Schulz | Assigned To | => Ina Schieferdecker
13-10-2007 19:20 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Jens Grabowski
15-10-2007 13:15 | Ina Schieferdecker | Note Added: 0003612 |
15-10-2007 15:22 | Ina Schieferdecker | Note Added: 0003617 |
18-10-2007 14:27 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
12-08-2008 16:28 | Jens Grabowski | File Added: CR-0413-Static-Test-Configurations.ppt |
12-08-2008 16:28 | Jens Grabowski | Note Added: 0006501 |
12-12-2008 09:04 | Ina Schieferdecker | Relationship added | related to 0004275
12-12-2008 09:25 | Ina Schieferdecker | Relationship added | related to 0000381
12-12-2008 09:26 | Ina Schieferdecker | Relationship added | related to 0002143
12-12-2008 09:27 | Ina Schieferdecker | Relationship added | related to 0002758
13-01-2009 11:41 | Ina Schieferdecker | File Added: es_TTCN3PackageTemplate_Configuration-V1_JG_TD.doc |
15-01-2009 17:16 | Jens Grabowski | File Added: es_TTCN3PackageTemplate_Configuration-V2-090115.doc |
21-04-2009 11:58 | Ina Schieferdecker | File Added: TRI and TCI for DeplConfig.ppt |
21-04-2009 11:58 | Ina Schieferdecker | Note Added: 0008524 |
21-04-2009 18:18 | Ina Schieferdecker | Note Added: 0008530 |
21-04-2009 18:18 | Ina Schieferdecker | File Added: TRI and TCI for DeplConfig_v2.ppt |
23-04-2009 14:40 | Ina Schieferdecker | Note Added: 0008551 |
23-04-2009 14:41 | Ina Schieferdecker | File Added: es202781_DeploymentConfiguration_220409.doc |
21-01-2010 15:31 | Jens Grabowski | File Added: Deployment-Semantics-100120.doc |
21-01-2010 15:32 | Jens Grabowski | Note Added: 0009163 |
21-01-2010 17:10 | Jens Grabowski | File Added: es202781_DeploymentConfiguration-100121-complete.zip |
21-01-2010 17:11 | Jens Grabowski | Note Added: 0009164 |
22-01-2010 10:30 | Jens Grabowski | File Added: es202781_DeploymentConfiguration-100122-complete.zip |
22-01-2010 10:31 | Jens Grabowski | Note Added: 0009165 |
16-02-2010 14:36 | Jens Grabowski | Status | assigned => closed
16-02-2010 14:36 | Jens Grabowski | Note Added: 0009223 |
16-02-2010 14:36 | Jens Grabowski | Resolution | open => fixed

Notes

(0003612)
Ina Schieferdecker
15-10-2007 13:15

to be considered together with CR 419

(0003617)
Ina Schieferdecker
15-10-2007 15:22

deferred to 2008

(0006501)
Jens Grabowski
12-08-2008 16:28

Slides for discussion uploaded!

(0008524)
Ina Schieferdecker
21-04-2009 11:58

Initial thoughts on the TRI/TCI support for the depl&conf. package as a basis for discussion.

(0008530)
Ina Schieferdecker
21-04-2009 18:18

Revision of the TRI/TCI interface after discussion: 1. use dedicated TRI/TCI map/connect operations for static connections 2. enable the handling of static configurations via TM in order to support the starting of test cases with static configurations from TM

(0008551)
Ina Schieferdecker
23-04-2009 14:40

Definition of TRI/TCI according to discussion:
TRI:
changes to triExecuteTestCase not to handle static maps
changes to triUnmap to cope with static maps
definition of triStaticMap
Definition of Java, C, and C++ mapping
TCI:
extension to TciTestComponentKindType
TCI TM required - definition of tciStartConfig and tciKillConfig
TCI TM provided - definition of tciConfigStarted and tciConfigKilled
TCI CH required - definition of tciStaticConnect and tciStaticMap
- tciDisconnect and TciUnmap to handle also static connections
TCI CH provided - definition of tciStaticConnectReq and tciStaticMapReq
- tciDisconnectReq and TciUnmapReq to handle also static connections
TCI-TL provided - definition of
tliCStaticCreate, tliPStaticConnect, and tliPStaticMap
- definition of tliConfigStarted and tliConfigKilled
Definition of Java, C, C++, and XML mapping

(0009163)
Jens Grabowski
21-01-2010 15:32

Deployment-Semantics-100120.doc includes the operational semantics of the static test configuration package as a delta to part 4 of the TTCN-3 standard.

(0009164)
Jens Grabowski
21-01-2010 17:11

es202781_DeploymentConfiguration-100121-complete.zip includes the Deployment and Configuration package including the operational semantics.

(0009165)
Jens Grabowski
22-01-2010 10:31

Update from 22 Jan 2010 includes a few editorial corrections.

(0009223)
Jens Grabowski
16-02-2010 14:36

First version of the package is completed and uploaded. The CR is closed for the moment.