Hi all,
The broken link has been fixed on the
www.ttcn-3.org site .. so Antti's
thesis is again downloadable.
Sorry about that,
stephan
>
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 Antti Hyrkkanen
> Sent: 05 March 2007 09:41
> To: TTCN3
> Subject: Re: multiple system adapters in TTCN-3?
>
> Hello Venkita
>
> I'd recommend to implement your SA in such a way that it is a
> kind of=20 super-SA that provides a framework or skeleton
> code for several=20 different SAs. The super-SA implements
> the TRI interface which=20 does multiplexin between the TE
> and the SAs. Each SA then provides=20 different means to
> communicate with different SUTs or to control any=20 other
> entities you might need in your testing. You also might want
> an=20 unified interface at TTCN-3 core language level via
> which you can=20 address or communicate with the different SAs.
>
> This is only my personal opinion how it should and could be
> done,=20 since I don't see point in writing several separate
> adapters and not=20 to have the possibility to use their
> combined functionality in a=20 single testcase. It does some
> take some extra time to write the=20 framework code, but
> that's only done once.
>
> > >> to interact with a database and another to interact with a HTTP
> > >> application. Now I may want to reuse both of these in a
> different
> > >> context. So can these system adapters co-exist or should I wrap
> > >> the two under a single system adapter?
>
>
> One day you might have a SUT that has both the
> database-interface and=20 the HTTP-interface, and you might
> want to access both interfaces in a=20 single testcase. If
> you then have this super-SA at hand, you can pat=20 yourself
> on shoulder and say great work pal.
>
> I can email you my thesis work which specifies one way to
> implement=20 this super-SA structure at TTCN-3 and adapter
> level. It's also on the=20 ETSI TTCN-3 page but the link is
> currently broken.
>
> My approach is a bit like what Vesa-Matti described what can
> be done=20 with OpenTTCN Tester, with the difference that
> multiplexing in=20 OpenTTCN is done by the tool itself, and
> in my approach it is done by=20 the hand written super-SA
> that can be used with any tool. I've also=20 tried to specify
> a unified control interface at TTCN-3 language level=20 to
> the different SAs.
>
> Br
> Antti
>
> // Antti Hyrkk=E4nen @ Plenware
> //
www.plenware.fi/en
>
> >
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 Theofanis =
> Vassiliou-Gioles
> > Sent: 2. maaliskuuta 2007 17:11
> > To:
This email address is being protected from spambots. You need JavaScript enabled to view it.
> > Subject: Re: multiple system adapters in TTCN-3?
> >=20
> > Hi,
> >=20
> > so if I got you right, you provide two default wrapper =
> functionalities,
> > one that does nothing and forwards all TRI request to the same TSI
> > instance, and another that selects the implementation according to =
> some
> > proprietary selection mechanism (e.g port type, port name, etc).
> >=20
> > Best regards, Theo
> >=20
> >=20
> > Vesa-Matti Puro schrieb:
> > > Hello,
> > >
> > > TTCN-3 standard defines a single test system interface
> > > (TSI) to be used by an individual test case.
> > >
> > > It is then matter of implementation of a specific
> > > TTCN-3 tool if this single TSI can be implemented using
> only one or
> > > multiple System Under Test (SUT)
> > > adapter(s) and if these adapters are separate threads or separate
> > > processes etc.
> > >
> > > For example, OpenTTCN Tester for TTCN-3 allows you to
> select if you
> > > want implement each TSI port in the same SUT adapter or if you
> > > select to implement individual TSI ports in separate SUT adapters.
> > > Here each separate SUT adapter is a separate executable that is
> > > registered dynamically to the test system allowing re-use of the
> > > same adapter in different testing configurations and test
> systems.
> > > As you mentioned one of the SUT adapters could be DB
> adapter and the
> > > other HTTP adapter.
> > > The same registration method in OpenTTCN applies to external
> > > functions and platform adapters as well.
> > >
> > > Kind regards,
> > > Vesa-Matti
> > >
> > > --- Venkita Subramonian <
This email address is being protected from spambots. You need JavaScript enabled to view it.> wrote:
> > >
> > >> Hi,
> > >>
> > >> Can there be more than one system adapter co-existing in
> the TTCN-3
> > >> architecture? For example, I may have
> > >> 2 system adapters built for different purposes - eg.
> > >> one
> > >> to interact with a database and another to interact with a HTTP
> > >> application. Now I may want to reuse both of these in a
> different
> > >> context. So can these system adapters co-exist or should I wrap
> > >> the two under a single system adapter?
> > >>
> > >> Thanks
> > >> Venkita
> > >>
> > >
>
