ETSI's Bug Tracker - Ext Pack: Config & Deployment Support (ES 202 781)
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0006415 | Ext Pack: Config & Deployment Support (ES 202 781) | Clarification | public | 24-01-2013 10:51 | 26-12-2013 14:00

Reporter | Janek Nikolajev |
Assigned To | Jens Grabowski |
Priority | normal | Severity | minor | Reproducibility | always
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v1.1.1 (published 2010-08) |
Target Version | v1.3.1 (published 2014-06) | Fixed in Version |  |
Clause Reference(s) | 5.8
Source (company - Author) | Janek
TS version | 1.1.1

Summary | 0006415: Static PTC behaviour state between test cases

Description

In clause 5.8 "Executing test cases on static test configurations"
It is not clear what should happen to running behaviour of static PTCs in case the test case ends.
The question also applies to running timers.
Should all running PTCs be implicitly stopped, or continue running between test cases?
In case of timers(and component variables), the specification says: "They remain in the same state as when they were left after the creation
of the static test configuration or after the termination of a previous test case".
Does that mean that a running timer should continue running, but cannot change state to "timeout", since this will violate the same rule?

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR6415.doc (173,568) 29-11-2013 12:59 http://oldforge.etsi.org/mantis/file_download.php?file_id=2963&type=bug

Issue History
Date Modified | Username | Field | Change
24-01-2013 10:51 | Janek Nikolajev | New Issue |
24-01-2013 10:51 | Janek Nikolajev | Clause Reference(s) | => 5.8
24-01-2013 10:51 | Janek Nikolajev | Source (company - Author) | => Janek
24-01-2013 10:51 | Janek Nikolajev | TS version | => 1.1.1
25-03-2013 10:10 | Tomas Urban | Note Added: 0011340 |
08-07-2013 15:47 | Jens Grabowski | Status | new => assigned
08-07-2013 15:47 | Jens Grabowski | Assigned To | => Jens Grabowski
08-07-2013 18:16 | Gyorgy Rethy | Target Version | => v1.3.1 (published 2014-06)
28-11-2013 12:55 | Jacob Wieland - Spirent | Note Added: 0011859 |
29-11-2013 12:55 | Jacob Wieland - Spirent | File Added: CR6415.doc |
29-11-2013 12:59 | Jacob Wieland - Spirent | File Deleted: CR6415.doc |
29-11-2013 12:59 | Jacob Wieland - Spirent | File Added: CR6415.doc |
29-11-2013 13:02 | Jacob Wieland - Spirent | Note Added: 0011870 |
29-11-2013 13:02 | Jacob Wieland - Spirent | Status | assigned => confirmed
26-12-2013 13:59 | Jens Grabowski | Note Added: 0011905 |
26-12-2013 14:00 | Jens Grabowski | Status | confirmed => closed
26-12-2013 14:00 | Jens Grabowski | Resolution | open => fixed

Notes

(0011340)
Tomas Urban
25-03-2013 10:10

Having active SUT-related behaviour in between test cases is not a good idea. For that reason, I suppose that the simplest solution of the issue is to stop behaviour running on all parallel static components when MTC stops.
Proposal:
The current rule saying that "Furthermore, all non-static test components, non-static connections and all non static mappings shall be discarded." shall be changed to: "Furthermore, all behaviour running on parallel static components shall be implicitly stopped and non-static test components, non-static connections and all non static mappings shall be discarded."
Regarding timers:
The following rule shall be amended:
"They remain in the same state as when they were left after the creation
of the static test configuration or after the termination of a previous test case."
-->
"They remain in the same state as when they were left after the creation
of the static test configuration or after the termination of a previous test case with exception of running timers which can change their state from running to timeout."

(0011859)
Jacob Wieland - Spirent
28-11-2013 12:55

I think the test components should be stopped. No behavior should be running between test cases. The SUT can still enqueue messages at the components' ports but they can at the earliest be processed during the course of the next testcases. The same is true for static mappings before the first testcase invocation on a static configuration.
I a timer can continue running and change its internal state to timeout (i.e. be put in the timeout queue). Again, this state change can only be observed from an actually running behavior at the earliest during the next testcase.

(0011870)
Jacob Wieland - Spirent
29-11-2013 13:02

Re-affirmed that also for test cases on static configuration, all ptcs are stopped when the test case terminates (as for normal test cases). There is no behavior between test cases running. Also added that timers can time out even after the termination (but the timeout can only be observed in a following test case). Same for messages from the SUT to static ports.

(0011905)
Jens Grabowski
26-12-2013 13:59

Implemented as suggested.