Hi,



In the next situation,



1.- In the behaviour of MTC, PTC1 is created.

2.- In the behaviour of PTC1, PTC2 is created.

3.- In the behaviour of MTC, stop the PTC1 (PTC1.stop)



Should PTC2 be stopped too with the statement PTC1.stop? Is this behaviour
equivalent if PTC1 is an alive-type component or non-alive-type?



Thanks.



Raúl Alfonso Quintana

Hi Raul,

if I understood correctly your setting:

PTC2 keeps executing, when PTC1 is being stopped.

This has nothing to do with PTC1 being alive or not.

PTCs are independent from each other - there is e.g. no parent-child-relation.

Only the MTC is different - if the MTC stops all PTCs stop as well.

Best regards,

Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

________________________________

From: active_ttcn3 : mts stf133 ttcn version 3 - active members only [This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Raúl Alfonso Quintana
Sent: Thursday, May 14, 2009 1:14 PM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Stop test behaviour operation



Hi,



In the next situation,



1.- In the behaviour of MTC, PTC1 is created.

2.- In the behaviour of PTC1, PTC2 is created.

3.- In the behaviour of MTC, stop the PTC1 (PTC1.stop)



Should PTC2 be stopped too with the statement PTC1.stop? Is this behaviour equivalent if PTC1 is an alive-type component or non-alive-type?



Thanks.



Raúl Alfonso Quintana

Hi Ina,



Thanks for your answer, but if there isn’t no parent-child-relation, I don’t
understand how MTC can stop a PTC that it doesn’t know. I’m thinking in a
distributed system where MTC is in TE*, PTC1 in TE1 and PTC2 in TE2. When
PTC2 is created, TE1 (CH Required) call to tciCreateTestComponentReq that
return the TriComponentId of PTC2 to TE1. The TE* don’t know the
TriComponentId of PTC2, so it can’t call to tciStopTestComponentReq(PTC2). I
haven’t found a tci operation to stop all PTC’s and I don’t know how to do
it through “tci”. I have searched about this in archives of list on
list.etsi.org and I have found the item 001307 where are talking about it,
but I don’t found any solution.



Thanks,



Raúl



_____

De: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] En nombre de Schieferdecker, Ina
Enviado el: jueves, 14 de mayo de 2009 13:32
Para: This email address is being protected from spambots. You need JavaScript enabled to view it.
Asunto: Re: Stop test behaviour operation



Hi Raul,



if I understood correctly your setting:



PTC2 keeps executing, when PTC1 is being stopped.



This has nothing to do with PTC1 being alive or not.



PTCs are independent from each other - there is e.g. no
parent-child-relation.



Only the MTC is different - if the MTC stops all PTCs stop as well.


Best regards,



Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

_____


From: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Raúl Alfonso Quintana
Sent: Thursday, May 14, 2009 1:14 PM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Stop test behaviour operation

Hi,



In the next situation,



1.- In the behaviour of MTC, PTC1 is created.

2.- In the behaviour of PTC1, PTC2 is created.

3.- In the behaviour of MTC, stop the PTC1 (PTC1.stop)



Should PTC2 be stopped too with the statement PTC1.stop? Is this behaviour
equivalent if PTC1 is an alive-type component or non-alive-type?



Thanks.



Raúl Alfonso Quintana

Hi Raul,

all component creation and termination goes via CH. So does mtc.stop. By that, the CH can issue stop for the PTCs. There are different approaches how to do this - at the buttom it is just CH knowing where the PTCs are.

With best regards,

Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

________________________________

From: active_ttcn3 : mts stf133 ttcn version 3 - active members only [This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Raúl Alfonso Quintana
Sent: Thursday, May 14, 2009 2:35 PM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Re: Stop test behaviour operation



Hi Ina,



Thanks for your answer, but if there isn't no parent-child-relation, I don't understand how MTC can stop a PTC that it doesn't know. I'm thinking in a distributed system where MTC is in TE*, PTC1 in TE1 and PTC2 in TE2. When PTC2 is created, TE1 (CH Required) call to tciCreateTestComponentReq that return the TriComponentId of PTC2 to TE1. The TE* don't know the TriComponentId of PTC2, so it can't call to tciStopTestComponentReq(PTC2). I haven't found a tci operation to stop all PTC's and I don't know how to do it through "tci". I have searched about this in archives of list on list.etsi.org and I have found the item 001307 where are talking about it, but I don't found any solution.



Thanks,



Raúl




________________________________


De: active_ttcn3 : mts stf133 ttcn version 3 - active members only [This email address is being protected from spambots. You need JavaScript enabled to view it.] En nombre de Schieferdecker, Ina
Enviado el: jueves, 14 de mayo de 2009 13:32
Para: This email address is being protected from spambots. You need JavaScript enabled to view it.
Asunto: Re: Stop test behaviour operation



Hi Raul,



if I understood correctly your setting:



PTC2 keeps executing, when PTC1 is being stopped.



This has nothing to do with PTC1 being alive or not.



PTCs are independent from each other - there is e.g. no parent-child-relation.



Only the MTC is different - if the MTC stops all PTCs stop as well.


Best regards,



Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

________________________________


From: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Raúl Alfonso Quintana
Sent: Thursday, May 14, 2009 1:14 PM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Stop test behaviour operation

Hi,



In the next situation,



1.- In the behaviour of MTC, PTC1 is created.

2.- In the behaviour of PTC1, PTC2 is created.

3.- In the behaviour of MTC, stop the PTC1 (PTC1.stop)



Should PTC2 be stopped too with the statement PTC1.stop? Is this behaviour equivalent if PTC1 is an alive-type component or non-alive-type?



Thanks.



Raúl Alfonso Quintana

Hi Ina,



When you want stop the testcase there isn’t problem, you can do mtc.stop and
CH resolve the problem. But when in the behaviour of MTC (the testcase) you
write “all component.stop” the MTC stops all PTCs of the testcase but not
itself. How does the TE of MTC tell CH “stop all PTC’s but not stop MTC”?



Thanks.



Best regards,



Raúl



_____

De: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] En nombre de Schieferdecker, Ina
Enviado el: jueves, 14 de mayo de 2009 14:39
Para: This email address is being protected from spambots. You need JavaScript enabled to view it.
Asunto: Re: Stop test behaviour operation



Hi Raul,



all component creation and termination goes via CH. So does mtc.stop. By
that, the CH can issue stop for the PTCs. There are different approaches how
to do this - at the buttom it is just CH knowing where the PTCs are.



With best regards,



Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

_____


From: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Raúl Alfonso Quintana
Sent: Thursday, May 14, 2009 2:35 PM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Re: Stop test behaviour operation

Hi Ina,



Thanks for your answer, but if there isn’t no parent-child-relation, I don’t
understand how MTC can stop a PTC that it doesn’t know. I’m thinking in a
distributed system where MTC is in TE*, PTC1 in TE1 and PTC2 in TE2. When
PTC2 is created, TE1 (CH Required) call to tciCreateTestComponentReq that
return the TriComponentId of PTC2 to TE1. The TE* don’t know the
TriComponentId of PTC2, so it can’t call to tciStopTestComponentReq(PTC2). I
haven’t found a tci operation to stop all PTC’s and I don’t know how to do
it through “tci”. I have searched about this in archives of list on
list.etsi.org and I have found the item 001307 where are talking about it,
but I don’t found any solution.



Thanks,



Raúl




_____


De: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] En nombre de Schieferdecker, Ina
Enviado el: jueves, 14 de mayo de 2009 13:32
Para: This email address is being protected from spambots. You need JavaScript enabled to view it.
Asunto: Re: Stop test behaviour operation



Hi Raul,



if I understood correctly your setting:



PTC2 keeps executing, when PTC1 is being stopped.



This has nothing to do with PTC1 being alive or not.



PTCs are independent from each other - there is e.g. no
parent-child-relation.



Only the MTC is different - if the MTC stops all PTCs stop as well.


Best regards,



Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

_____


From: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Raúl Alfonso Quintana
Sent: Thursday, May 14, 2009 1:14 PM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Stop test behaviour operation

Hi,



In the next situation,



1.- In the behaviour of MTC, PTC1 is created.

2.- In the behaviour of PTC1, PTC2 is created.

3.- In the behaviour of MTC, stop the PTC1 (PTC1.stop)



Should PTC2 be stopped too with the statement PTC1.stop? Is this behaviour
equivalent if PTC1 is an alive-type component or non-alive-type?



Thanks.



Raúl Alfonso Quintana

Hi Raul,

The statement "all component.stop" has a specific meaning in "core
language". As follow:

"all component.stop; Stop the behaviour on all PTCs; from MTC only"
which is adapted from Table 19: Any and All with components from core
language v3.4.1(2008.9)

Thanks

xuezhi



2009/5/14 Raúl Alfonso Quintana <This email address is being protected from spambots. You need JavaScript enabled to view it.>

> Hi Ina,
>
>
>
> When you want stop the testcase there isn’t problem, you can do mtc.stop
> and CH resolve the problem. But when in the behaviour of MTC (the testcase)
> you write “all component.stop” the MTC stops all PTCs of the testcase but
> not itself. How does the TE of MTC tell CH “stop all PTC’s but not stop
> MTC”?
>
>
>
> Thanks.
>
>
>
> Best regards,
>
>
>
> Raúl
>
>
>

---

>
> *De:* active_ttcn3 : mts stf133 ttcn version 3 - active members only
> [This email address is being protected from spambots. You need JavaScript enabled to view it.] *En nombre de *Schieferdecker, Ina
> *Enviado el:* jueves, 14 de mayo de 2009 14:39
>
> *Para:* This email address is being protected from spambots. You need JavaScript enabled to view it.
> *Asunto:* Re: Stop test behaviour operation
>
>
>
> Hi Raul,
>
>
>
> all component creation and termination goes via CH. So does mtc.stop. By
> that, the CH can issue stop for the PTCs. There are different approaches how
> to do this - at the buttom it is just CH knowing where the PTCs are.
>
>
>
> With best regards,
>
>
>
> Ina
>
>
>
>

---

> Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
> Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
> Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
> Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
> D-10589 Berlin fax: ++49-30-3463-8241
>

---

>
>
>
>
>

---

>
> *From:* active_ttcn3 : mts stf133 ttcn version 3 - active members only
> [This email address is being protected from spambots. You need JavaScript enabled to view it.] *On Behalf Of *Raúl Alfonso Quintana
> *Sent:* Thursday, May 14, 2009 2:35 PM
> *To:* This email address is being protected from spambots. You need JavaScript enabled to view it.
> *Subject:* Re: Stop test behaviour operation
>
> Hi Ina,
>
>
>
> Thanks for your answer, but if there isn’t no parent-child-relation, I
> don’t understand how MTC can stop a PTC that it doesn’t know. I’m thinking
> in a distributed system where MTC is in TE*, PTC1 in TE1 and PTC2 in TE2.
> When PTC2 is created, TE1 (CH Required) call to tciCreateTestComponentReq
> that return the TriComponentId of PTC2 to TE1. The TE* don’t know the
> TriComponentId of PTC2, so it can’t call to tciStopTestComponentReq(PTC2). I
> haven’t found a tci operation to stop all PTC’s and I don’t know how to do
> it through “tci”. I have searched about this in archives of list on
> list.etsi.org and I have found the item 001307 where are talking about it,
> but I don’t found any solution.
>
>
>
> Thanks,
>
>
>
> Raúl
>
>
>

---

>
> *De:* active_ttcn3 : mts stf133 ttcn version 3 - active members only
> [This email address is being protected from spambots. You need JavaScript enabled to view it.] *En nombre de *Schieferdecker, Ina
> *Enviado el:* jueves, 14 de mayo de 2009 13:32
> *Para:* This email address is being protected from spambots. You need JavaScript enabled to view it.
> *Asunto:* Re: Stop test behaviour operation
>
>
>
> Hi Raul,
>
>
>
> if I understood correctly your setting:
>
>
>
> PTC2 keeps executing, when PTC1 is being stopped.
>
>
>
> This has nothing to do with PTC1 being alive or not.
>
>
>
> PTCs are independent from each other - there is e.g. no
> parent-child-relation.
>
>
>
> Only the MTC is different - if the MTC stops all PTCs stop as well.
>
>
> Best regards,
>
>
>
> Ina
>
>
>
>

---

> Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
> Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
> Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
> Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
> D-10589 Berlin fax: ++49-30-3463-8241
>

---

>
>
>
>
>

---

>
> *From:* active_ttcn3 : mts stf133 ttcn version 3 - active members only
> [This email address is being protected from spambots. You need JavaScript enabled to view it.] *On Behalf Of *Raúl Alfonso Quintana
> *Sent:* Thursday, May 14, 2009 1:14 PM
> *To:* This email address is being protected from spambots. You need JavaScript enabled to view it.
> *Subject:* Stop test behaviour operation
>
> Hi,
>
>
>
> In the next situation,
>
>
>
> 1.- In the behaviour of MTC, PTC1 is created.
>
> 2.- In the behaviour of PTC1, PTC2 is created.
>
> 3.- In the behaviour of MTC, stop the PTC1 (PTC1.stop)
>
>
>
> Should PTC2 be stopped too with the statement PTC1.stop? Is this behaviour
> equivalent if PTC1 is an alive-type component or non-alive-type?
>
>
>
> Thanks.
>
>
>
> Raúl Alfonso Quintana
>
>
>
>
>
>
>
>
>
>
>
>

Hi Raul,

I was away ... tciStopTestComponent uses TriComponentIdType ... please have a look at TRI:


NOTE 1: For the handling of TCI operations on any or all components, the component type name can also be set to "ANY" or "ALL". In that case, both the identifier and the component name are to be ignored.

With best regards,

Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

________________________________

From: active_ttcn3 : mts stf133 ttcn version 3 - active members only [This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of xuezhi xing
Sent: Friday, May 15, 2009 3:22 AM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Re: Stop test behaviour operation


Hi Raul,

The statement "all component.stop" has a specific meaning in "core language". As follow:

"all component.stop; Stop the behaviour on all PTCs; from MTC only"

which is adapted from Table 19: Any and All with components from core language v3.4.1(2008.9)

Thanks

xuezhi



2009/5/14 Raúl Alfonso Quintana <This email address is being protected from spambots. You need JavaScript enabled to view it.>


Hi Ina,



When you want stop the testcase there isn't problem, you can do mtc.stop and CH resolve the problem. But when in the behaviour of MTC (the testcase) you write "all component.stop" the MTC stops all PTCs of the testcase but not itself. How does the TE of MTC tell CH "stop all PTC's but not stop MTC"?



Thanks.



Best regards,



Raúl




________________________________


De: active_ttcn3 : mts stf133 ttcn version 3 - active members only [This email address is being protected from spambots. You need JavaScript enabled to view it.] En nombre de Schieferdecker, Ina
Enviado el: jueves, 14 de mayo de 2009 14:39

Para: This email address is being protected from spambots. You need JavaScript enabled to view it.
Asunto: Re: Stop test behaviour operation







Hi Raul,



all component creation and termination goes via CH. So does
mtc.stop. By that, the CH can issue stop for the PTCs. There are different approaches how to do this - at the buttom it is just CH knowing where the PTCs are.



With best regards,



Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

________________________________


From: active_ttcn3 : mts stf133 ttcn version 3 - active
members only [This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Raúl Alfonso Quintana
Sent: Thursday, May 14, 2009 2:35 PM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Re: Stop test behaviour operation

Hi Ina,



Thanks for your answer, but if there isn't no parent-child-
relation, I don't understand how MTC can stop a PTC that it doesn't know. I'm thinking in a distributed system where MTC is in TE*, PTC1 in TE1 and PTC2 in TE2. When PTC2 is created, TE1 (CH Required) call to tciCreateTestComponentReq that return the TriComponentId of PTC2 to TE1. The TE* don't know the TriComponentId of PTC2, so it can't call to tciStopTestComponentReq(PTC2). I haven't found a tci operation to stop all PTC's and I don't know how to do it through "tci". I have searched about this in archives of list on list.etsi.org <list.etsi.org/> and I have found the item 001307 where are talking about it, but I don't found any solution.



Thanks,



Raúl




________________________________


De: active_ttcn3 : mts stf133 ttcn version 3 - active members
only [This email address is being protected from spambots. You need JavaScript enabled to view it.] En nombre de Schieferdecker, Ina
Enviado el: jueves, 14 de mayo de 2009 13:32
Para: This email address is being protected from spambots. You need JavaScript enabled to view it.
Asunto: Re: Stop test behaviour operation



Hi Raul,



if I understood correctly your setting:



PTC2 keeps executing, when PTC1 is being stopped.



This has nothing to do with PTC1 being alive or not.



PTCs are independent from each other - there is e.g. no parent-child-relation.



Only the MTC is different - if the MTC stops all PTCs stop as
well.


Best regards,



Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

________________________________


From: active_ttcn3 : mts stf133 ttcn version 3 - active
members only [This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Raúl Alfonso Quintana
Sent: Thursday, May 14, 2009 1:14 PM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Stop test behaviour operation

Hi,



In the next situation,



1.- In the behaviour of MTC, PTC1 is created.

2.- In the behaviour of PTC1, PTC2 is created.

3.- In the behaviour of MTC, stop the PTC1 (PTC1.stop)



Should PTC2 be stopped too with the statement PTC1.stop?
Is this behaviour equivalent if PTC1 is an alive-type component or non-alive-type?



Thanks.



Raúl Alfonso Quintana

Hi Ina,



Thanks for your answer.



Best regards,



Raúl

_____

De: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] En nombre de Schieferdecker, Ina
Enviado el: viernes, 15 de mayo de 2009 8:54
Para: This email address is being protected from spambots. You need JavaScript enabled to view it.
Asunto: Re: Stop test behaviour operation



Hi Raul,



I was away ... tciStopTestComponent uses TriComponentIdType ... please have
a look at TRI:



NOTE 1: For the handling of TCI operations on any or all components,
the component type name can also be set to "ANY" or "ALL". In that case,
both the identifier and the component name are to be ignored.

With best regards,



Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

_____


From: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of xuezhi xing
Sent: Friday, May 15, 2009 3:22 AM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Re: Stop test behaviour operation

Hi Raul,



The statement "all component.stop" has a specific meaning in "core
language". As follow:



"all component.stop; Stop the behaviour on all PTCs; from MTC only"

which is adapted from Table 19: Any and All with components from core
language v3.4.1(2008.9)



Thanks



xuezhi






2009/5/14 Raúl Alfonso Quintana <This email address is being protected from spambots. You need JavaScript enabled to view it.>

Hi Ina,



When you want stop the testcase there isn’t problem, you can do mtc.stop and
CH resolve the problem. But when in the behaviour of MTC (the testcase) you
write “all component.stop” the MTC stops all PTCs of the testcase but not
itself. How does the TE of MTC tell CH “stop all PTC’s but not stop MTC”?



Thanks.



Best regards,



Raúl




_____


De: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] En nombre de Schieferdecker, Ina
Enviado el: jueves, 14 de mayo de 2009 14:39


Para: This email address is being protected from spambots. You need JavaScript enabled to view it.
Asunto: Re: Stop test behaviour operation



Hi Raul,



all component creation and termination goes via CH. So does mtc.stop. By
that, the CH can issue stop for the PTCs. There are different approaches how
to do this - at the buttom it is just CH knowing where the PTCs are.



With best regards,



Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

_____


From: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Raúl Alfonso Quintana
Sent: Thursday, May 14, 2009 2:35 PM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Re: Stop test behaviour operation

Hi Ina,



Thanks for your answer, but if there isn’t no parent-child-relation, I don’t
understand how MTC can stop a PTC that it doesn’t know. I’m thinking in a
distributed system where MTC is in TE*, PTC1 in TE1 and PTC2 in TE2. When
PTC2 is created, TE1 (CH Required) call to tciCreateTestComponentReq that
return the TriComponentId of PTC2 to TE1. The TE* don’t know the
TriComponentId of PTC2, so it can’t call to tciStopTestComponentReq(PTC2). I
haven’t found a tci operation to stop all PTC’s and I don’t know how to do
it through “tci”. I have searched about this in archives of list on
list.etsi.org <list.etsi.org/> and I have found the item 001307
where are talking about it, but I don’t found any solution.



Thanks,



Raúl




_____


De: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] En nombre de Schieferdecker, Ina
Enviado el: jueves, 14 de mayo de 2009 13:32
Para: This email address is being protected from spambots. You need JavaScript enabled to view it.
Asunto: Re: Stop test behaviour operation



Hi Raul,



if I understood correctly your setting:



PTC2 keeps executing, when PTC1 is being stopped.



This has nothing to do with PTC1 being alive or not.



PTCs are independent from each other - there is e.g. no
parent-child-relation.



Only the MTC is different - if the MTC stops all PTCs stop as well.


Best regards,



Ina

---

Prof. Dr.-Ing. Ina Schieferdecker, Head of Competence Center
Modeling and Testing url: www.fokus.fraunhofer.de/go/motion
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241

---

_____


From: active_ttcn3 : mts stf133 ttcn version 3 - active members only
[This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Raúl Alfonso Quintana
Sent: Thursday, May 14, 2009 1:14 PM
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Stop test behaviour operation

Hi,



In the next situation,



1.- In the behaviour of MTC, PTC1 is created.

2.- In the behaviour of PTC1, PTC2 is created.

3.- In the behaviour of MTC, stop the PTC1 (PTC1.stop)



Should PTC2 be stopped too with the statement PTC1.stop? Is this behaviour
equivalent if PTC1 is an alive-type component or non-alive-type?



Thanks.



Raúl Alfonso Quintana