Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: CH questions

CH questions 27 Jul 2007 08:49 #7163

Hello,

We are newbies in the world of TTCN and after reading tons of documents and
having seen some examples, it looks like if we are getting to understand it
except for the TCI component handling side. So we would appreciate some
guidance/orientation.

We have to test a system where several devices are involved. Our TSI groups
always include one of them + one or 2 of a different type.

The thing is that it is not very clear to us what the tci-ch provided
functions are suposed to do. Do they need to implement some logic, or,
having only one TE, should these functions just call the related required
function:
I.e.
tciStartTestComponentReq ... should just call the tciStartTestComponent on
the TE, or does it need to implement some business logic
tciMapReq -> tciMap
and so on.

Thank your very much ....

Vanessa
The administrator has disabled public write access.

CH questions 27 Jul 2007 09:40 #7164

Hello Vanessa,

The TCI-CH is used to implement distributed test execution, i.e. if the parallel test components are executed in different hosts. As long as you do not need such distributed execution, there should be no need for you to implement any functionality here. As long as there is no strict need to use distributed execution (e.g. the performance of a single host is not sufficient in your case, or you need different hosts because specific hardware interfaces are needed) you can simply have all parallel test components in a single executable.

As you need to connect to several devices, you can do the corresponding routing of messages or procedure calls (whatever is needed in your case) in the SUT adapter.

Btw., which tool are you using?

Best regards

Thomas

| Thomas Deiß |
| Nokia Networks GmbH |
| Meesmannstraße 103 |
| D-44807 Bochum |
| Mobile: +49 1639842217 |
| Direct: +49 2349842217 |
| Fax: +49 2349843491 |
| email: This email address is being protected from spambots. You need JavaScript enabled to view it. |


Nokia Networks GmbH
Sitz der Gesellschaft: Bochum
Amtsgericht Bochum: HRB 11180
Ust-Id.-Nr./ VAT ID: DE814765854
WEEE-Reg.-Nr. DE 51797011
Geschäftsführer: Dr. Ulrich Halka

Nokia Networks GmbH arbeitet auf Rechnung der Nokia Siemens Networks
Nokia Networks GmbH operates for the account of Nokia Siemens Networks



>
Original Message
>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 ext
>SUBSCRIBE TTCN3 Anonymous
>Sent: Friday, 27. July 2007 10:49
>To: This email address is being protected from spambots. You need JavaScript enabled to view it.
>Subject: CH questions
>
>Hello,
>
>We are newbies in the world of TTCN and after reading tons of
>documents a= nd having seen some examples, it looks like if we
>are getting to understand = it except for the TCI component
>handling side. So we would appreciate some guidance/orientation.
>
>We have to test a system where several devices are involved.
>Our TSI grou= ps always include one of them + one or 2 of a
>different type.
>
>The thing is that it is not very clear to us what the tci-ch
>provided functions are suposed to do. Do they need to
>implement some logic, or, having only one TE, should these
>functions just call the related required=
>
>function:
>I.e.
>tciStartTestComponentReq ... should just call the
>tciStartTestComponent o= n the TE, or does it need to
>implement some business logic tciMapReq -> tciMap and so on.
>
>Thank your very much ....
>
>Vanessa
>
The administrator has disabled public write access.

CH questions 27 Jul 2007 12:36 #7165

Hi Thomas,

Thanx a lot for your quick answer.

It makes the CH clearer now, I understand we would only need to implement
added functionality to the TC-CH for distributed test execution, but I am
still a bit confused about the components handling (creation, connection,
stop...) and what you mention about routing in the SUT Adapter ...

Our SUT adapter routes the messages to the device required in each case ,
but I cannot see the relation between that and connecting components.

About the tool we are using, we have ttcn-3 scripts already generated, and
we will use a Danet compiler. Also we are currently considering using
the T3DevKit
Codec Generator.

Kind regards, :)

Vanessa



2007/7/27, Thomas Deiss < This email address is being protected from spambots. You need JavaScript enabled to view it.>:
>
> Hello Vanessa,
>
> The TCI-CH is used to implement distributed test execution, i.e. if the
> parallel test components are executed in different hosts. As long as you do
> not need such distributed execution, there should be no need for you to
> implement any functionality here. As long as there is no strict need to use
> distributed execution ( e.g. the performance of a single host is not
> sufficient in your case, or you need different hosts because specific
> hardware interfaces are needed) you can simply have all parallel test
> components in a single executable.
>
> As you need to connect to several devices, you can do the corresponding
> routing of messages or procedure calls (whatever is needed in your case) in
> the SUT adapter.
>
> Btw., which tool are you using?
>
> Best regards
>
> Thomas
>
>
> | Thomas Deiß |
> | Nokia Networks GmbH |
> | Meesmannstraße 103 |
> | D-44807 Bochum |
> | Mobile: +49 1639842217 |
> | Direct: +49 2349842217 |
> | Fax: +49 2349843491 |
> | email: This email address is being protected from spambots. You need JavaScript enabled to view it. |
>
>
>
> Nokia Networks GmbH
> Sitz der Gesellschaft: Bochum
> Amtsgericht Bochum: HRB 11180
> Ust-Id.-Nr./ VAT ID: DE814765854
> WEEE-Reg.-Nr. DE 51797011
> Geschäftsführer: Dr. Ulrich Halka
>
> Nokia Networks GmbH arbeitet auf Rechnung der Nokia Siemens Networks
> Nokia Networks GmbH operates for the account of Nokia Siemens Networks
>
>
>
> >
Original Message
> >From: active_ttcn3 : mts stf133 ttcn version 3 - active
> >members only [mailto: This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of ext
> >SUBSCRIBE TTCN3 Anonymous
> >Sent: Friday, 27. July 2007 10:49
> >To: This email address is being protected from spambots. You need JavaScript enabled to view it.
> >Subject: CH questions
> >
> >Hello,
> >
> >We are newbies in the world of TTCN and after reading tons of
> >documents a= nd having seen some examples, it looks like if we
> >are getting to understand = it except for the TCI component
> >handling side. So we would appreciate some guidance/orientation.
> >
> >We have to test a system where several devices are involved.
> >Our TSI grou= ps always include one of them + one or 2 of a
> >different type.
> >
> >The thing is that it is not very clear to us what the tci-ch
> >provided functions are suposed to do. Do they need to
> >implement some logic, or, having only one TE, should these
> >functions just call the related required=
> >
> >function:
> >I.e.
> >tciStartTestComponentReq ... should just call the
> >tciStartTestComponent o= n the TE, or does it need to
> >implement some business logic tciMapReq -> tciMap and so on.
> >
> >Thank your very much ....
> >
> >Vanessa
> >
>
The administrator has disabled public write access.

CH questions 27 Jul 2007 14:18 #7166

Hello Vanessa,

in case the parallel test components are executing on a single host then typically there is also a single SA. But if you have to connect to several devices, the messages have to be routed to these devices. Such functionality can be implemented in the SA and does not require to do anything with the CH.

Actually there are tool specific issues here and my knowledge of the Danet tool is limited. So, if somebody with experience of the Danet tool could comment whether there are tool specific issues, this would be good.

Best regards

Thomas


________________________________

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 ext Development Test
Sent: Friday, 27. July 2007 14:37
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Re: CH questions


Hi Thomas,

Thanx a lot for your quick answer.

It makes the CH clearer now, I understand we would only need to implement added functionality to the TC-CH for distributed test execution, but I am still a bit confused about the components handling (creation, connection, stop...) and what you mention about routing in the SUT Adapter ...

Our SUT adapter routes the messages to the device required in each case , but I cannot see the relation between that and connecting components.

About the tool we are using, we have ttcn-3 scripts already generated, and we will use a Danet compiler. Also we are currently considering using the T3DevKit Codec Generator.

Kind regards, :)

Vanessa




2007/7/27, Thomas Deiss < This email address is being protected from spambots. You need JavaScript enabled to view it.>:

Hello Vanessa,

The TCI-CH is used to implement distributed test execution, i.e. if
the parallel test components are executed in different hosts. As long as you do not need such distributed execution, there should be no need for you to implement any functionality here. As long as there is no strict need to use distributed execution ( e.g. the performance of a single host is not sufficient in your case, or you need different hosts because specific hardware interfaces are needed) you can simply have all parallel test components in a single executable.

As you need to connect to several devices, you can do the corresponding routing of messages or procedure calls (whatever is needed in your case) in the SUT adapter.

Btw., which tool are you using?

Best regards

Thomas

| Thomas Deiß |
| Nokia Networks GmbH |
| Meesmannstraße 103 |
| D-44807 Bochum |
| Mobile: +49 1639842217 |
| Direct: +49 2349842217 |
| Fax: +49 2349843491 |
| email: This email address is being protected from spambots. You need JavaScript enabled to view it. |


Nokia Networks GmbH
Sitz der Gesellschaft: Bochum
Amtsgericht Bochum: HRB 11180
Ust-Id.-Nr./ VAT ID: DE814765854
WEEE-Reg.-Nr. DE 51797011
Geschäftsführer: Dr. Ulrich Halka

Nokia Networks GmbH arbeitet auf Rechnung der Nokia Siemens
Networks
Nokia Networks GmbH operates for the account of Nokia Siemens
Networks



>
Original Message
>From: active_ttcn3 : mts stf133 ttcn version 3 - active
>members only [mailto: This email address is being protected from spambots. You need JavaScript enabled to view it. <This email address is being protected from spambots. You need JavaScript enabled to view it.> ] On Behalf Of ext
>SUBSCRIBE TTCN3 Anonymous
>Sent: Friday, 27. July 2007 10:49
>To: This email address is being protected from spambots. You need JavaScript enabled to view it.
>Subject: CH questions
>
>Hello,
>
>We are newbies in the world of TTCN and after reading tons of
>documents a= nd having seen some examples, it looks like if we
>are getting to understand = it except for the TCI component
>handling side. So we would appreciate some guidance/orientation.
>
>We have to test a system where several devices are involved.
>Our TSI grou= ps always include one of them + one or 2 of a
>different type.
>
>The thing is that it is not very clear to us what the tci-ch
>provided functions are suposed to do. Do they need to
>implement some logic, or, having only one TE, should these
>functions just call the related required=
>
>function:
>I.e.
>tciStartTestComponentReq ... should just call the
>tciStartTestComponent o= n the TE, or does it need to
>implement some business logic tciMapReq -> tciMap and so on.
>
>Thank your very much ....
>
>Vanessa
>
The administrator has disabled public write access.
  • Page:
  • 1

FacebookTwitterGoogle BookmarksRedditNewsvineTechnoratiLinkedin