ETSI's Bug Tracker - Ext Pack: Perf & Real Time Testing (ES 202 782)
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0000404 | Ext Pack: Perf & Real Time Testing (ES 202 782) | New Feature | public | 24-11-2006 13:59 | 24-05-2011 17:43

Reporter | Stephan Schulz |
Assigned To | Gyorgy Rethy |
Priority | low | Severity | feature | Reproducibility | N/A
Status | closed | Resolution | won't fix |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v1.2.1 (published 2014-06) | Fixed in Version |  |
Clause Reference(s) | 7.3.3.1.29
Source (company - Author) | Thomas deiss, nokia
TS version |

Summary | 0000404: Support for simulated time

Description

Solution for testing with simulated time So far, most TTCN-3 test suites have been executed using a notion of real-time. Implementing simulated time in TTCN-3 is not straightforward. In the TT-Medal project, we have provided three possible implementations of simulated time for TTCN-3 by Nokia, Conformiq and Centrum voor Wiskunde en Informatica. Although working well for certain case studies, these solutions are ad-hoc and not always efficient. All the solutions share the following common functionality: detecting idleness (either of the test system or of the test system together with the SUT) and progressing time by updating active timers. Here we consider a system consisting of several entities or components running in parallel. Each of the entities can be either active or idle. An active entity becomes idle if it cannot proceed by receiving/sending messages/timeouts or computations. An idle entity is activated by receiving a message, or a timeout or a call. The whole system is idle if all entities are idle and there are no messages and timeouts pending in the network. In simulated time, time may progress when the whole system is idle. In order to facilitate idleness detection, we propose to introduce an operation tciAllAWait(TRIcounter1, TRIcounter2, TCIcounter1, TCIcounter2) where the first two counters show the number of messages/calls/replys/exception/timeouts respectively sent and received by a TE entity via TRI interface. The second pair of counters provides the same information about messages exchanged via TCI. This operation is called by a TE when it awaits an event for a new snapshot meaning the TE cannot proceed by computation/sending/receiving messages. The idleness of a single TE does not necessarily mean the idleness of the whole system. There still can be a message sent by the SUT pending, or one of TEs can still be active sending messages to other TEs and/or the SUT. To decide on the global idleness the CH entity uses the information provided by tciAllAWait calls of the underlying TEs. The information given by the tciAllAWait can be exploited to detect idleness of the test system. For example one of the existing distributed termination detection algorithms can be implemented by the CH in order to decide on the idleness of the distributed test system. After the idleness of the test system is detected by the CH entity, two ways are possible at least. If the SUT provides an interface informing the CH on the idleness of the SUT, the CH decides on the global idleness of the test system and the SUT and triggers time progression. Otherwise, the CH entity reports on the idleness of the test system to the SUT and the SUT decides on the global idleness and triggers time progression. If the SUT is not idle it just activates the test system by sending a non-timed message. Both ways have been implemented in the case studies carried by Nokia, Conformiq and Centrum voor Wiskunde en Informatica in the TT-Medal project. Testing with simulated time have been successfully applied to test systems from railway and telecommunication. The main advantage of introducing the new interface is that it shifts idleness detection within a TE entity to an implementation of TE Executable. That enables using the same test suites for testing with real time and for testing with simulated time.

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

Relationships

related to | 0004483 | closed | Jens Grabowski | Part 01: TTCN-3 Core Language | New Concepts to Test Real Time Properties

Attached Files |

Issue History
Date Modified | Username | Field | Change
24-11-2006 13:59 | Stephan Schulz | New Issue |
24-11-2006 13:59 | Stephan Schulz | Clause Reference(s) | => 7.3.3.1.29
24-11-2006 13:59 | Stephan Schulz | Source (company - Author) | => Thomas deiss, nokia
15-06-2007 19:18 | Stephan Schulz | Status | new => assigned
15-06-2007 19:18 | Stephan Schulz | Assigned To | => Ina Schieferdecker
15-10-2007 17:09 | Ina Schieferdecker | Note Added: 0003626 |
18-10-2007 14:24 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
28-11-2008 12:31 | Ina Schieferdecker | Relationship added | related to 0004483
28-11-2008 12:32 | Ina Schieferdecker | Note Added: 0007500 |
28-11-2008 12:33 | Ina Schieferdecker | Target Version | Edition 4.1.1 (not yet published) => Edition 4.2.1 (not yet published)
20-04-2009 12:16 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Jens Grabowski
16-02-2010 14:37 | Jens Grabowski | Note Added: 0009224 |
18-03-2010 07:43 | Ina Schieferdecker | Target Version | Edition 4.2.1 (not yet published) => Edition 5.1.1 (not yet published)
22-03-2010 17:25 | Gyorgy Rethy | Assigned To | Jens Grabowski =>
22-03-2010 17:25 | Gyorgy Rethy | Status | assigned => new
23-03-2010 13:07 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
23-03-2010 13:07 | Gyorgy Rethy | Priority | normal => low
23-03-2010 13:07 | Gyorgy Rethy | Status | new => assigned
26-03-2010 10:36 | Gyorgy Rethy | Project | Part 06: TTCN-3 Control Interface => Ext Pack: Perf & Real Time Testing (ES 202 782)
30-11-2010 13:29 | Gyorgy Rethy | Note Added: 0009843 |
30-11-2010 13:29 | Gyorgy Rethy | Note Added: 0009844 |
30-11-2010 13:30 | Gyorgy Rethy | Note Added: 0009845 |
30-11-2010 13:30 | Gyorgy Rethy | Note Added: 0009846 |
30-11-2010 13:30 | Gyorgy Rethy | Note Added: 0009847 |
03-12-2010 09:48 | Gyorgy Rethy | Product Version | Edition 3.1.1 =>
03-12-2010 09:48 | Gyorgy Rethy | Target Version | Edition 4.3.1 (not yet published) => v1.3.1
13-12-2010 12:53 | Gyorgy Rethy | Target Version | v1.3.1 => v1.2.2 (interim)
24-05-2011 17:42 | Gyorgy Rethy | Note Added: 0010038 |
24-05-2011 17:43 | Gyorgy Rethy | Status | assigned => closed
24-05-2011 17:43 | Gyorgy Rethy | Note Added: 0010039 |
24-05-2011 17:43 | Gyorgy Rethy | Resolution | open => won't fix
26-05-2011 15:50 | Ina Schieferdecker | Relationship added | related to 0004275
26-05-2011 15:50 | Ina Schieferdecker | Relationship deleted | related to 0004275

Notes

(0003626)
Ina Schieferdecker
15-10-2007 17:09

to be deferred to the timing discussions for TTCN-3 in 2008

(0007500)
Ina Schieferdecker
28-11-2008 12:32

Resolution should consider the CR4483 resolution - hence targetted for v4.2.1

(0009224)
Jens Grabowski
16-02-2010 14:37

To be discussed for version 5.1.1.

(0009843)
Gyorgy Rethy
30-11-2010 13:29

STF discussion on 30/11/2010: postpone to 2011.

(0009844)
Gyorgy Rethy
30-11-2010 13:29

STF discussion on 30/11/2010: postpone to 2011.

(0009845)
Gyorgy Rethy
30-11-2010 13:30

STF discussion on 30/11/2010: postpone to 2011.

(0009846)
Gyorgy Rethy
30-11-2010 13:30

STF discussion on 30/11/2010: postpone to 2011.

(0009847)
Gyorgy Rethy
30-11-2010 13:30

STF discussion on 30/11/2010: postpone to 2011.

(0010038)
Gyorgy Rethy
24-05-2011 17:42

To be closed due to lack of input and interest.

(0010039)
Gyorgy Rethy
24-05-2011 17:43

Closed due to lack of input.