Hello Vesa-Matti et. al,
> Development of Interoperability and other in-house tests using
> TTCN would allow the re-use of the 3G test definitions (messages,
> constraints/templates) etc in these types of tests as well. Using modular
> TTCN, you can develop these tests as separate modules.
This is not an approach I would recommend to a user who is considering
TTCN2-3 migration. Apart from the fact that there are no defined semantics
for importing TTCN-2 types into a TTCN-3 module, there is also no
syntactical
support for using TTCN-2 constraints in TTCN-3 test cases.
This would have to be a proprietary tool solution, which obviously isn't in
the user's best interest when maintainability, portability and flexibility
is considered.
I'm not saying that existing TTCN-2 definitions cannot be reused, quite the
contrary: What you are mentioning, types and constraints, are the parts of
TTCN-2 that are easiest to translate into TTCN-3; In fact, it can be
automated, i.e done by a tool, and that is what a customer wants to do.
That way, he would end up with a standard-compliant test suite whose
contents
are supported by a variety of TTCN-3 tools, rather than a language mixture
with a questionable proprietary interpretation and not subject to
maintenance
by standardisation authorities.
> 'import from 3g_ue_test_module language "TTCN-2" all'
The "TTCN-2" attribute is not recognized in the TTCN-3 standard.
> In this way, you would use existing 3G UE tests as TTCN-2 without
> complex translation and you would be able develop your new tests
> using TTCN-3.
With the approach I proposed, the user would make the (non-complex
and automated) translation and get all the benefits of a modern and
living standard AND still obviously be able to develop his new tests
using TTCN-3.
> More details of this issue:
>
www.openttcn.com/Publications/Migration/
In your presentation at this location I find a disturbing note, to
which I must protest:
"TTCN-3 and TTCN-2 are both different presentation formats of the
same language"
This is downright wrong! Full stop. Some concepts from TTCN-2 have
been adopted, but No, TTCN-3 is a new and quite different language.
I don't think I need to go over the arguments for this, as they ought
to be familiar to most parties on this list, but statements like the
above mentioned gives a misleading and thoroughly incorrect message
to the market.
Also, the following conclusion troubles me:
" => no need to translate back and forth, the same TTCN tool you
are using will seamlessly support both"
I am not aware of any vendor who supplies such a tool, but you are
welcome to prove me wrong on this.
With best regards and Season's greetings,
/Johan
Tau Generation2 - Development Visualized. Productivity Realized.
Learn more about Telelogic's new system and software development
solution at:
www.taug2.com
Johan Nordin
Standardization specialist
Telelogic, Första Långgatan 19, SE-41327 Göteborg
Tel: +46 703 05 25 27 (currently inop, use +46 706 424711 until further
notice)
Email:
This email address is being protected from spambots. You need JavaScript enabled to view it.
URL:
www.telelogic.com/
Telelogic - Putting you ahead in development!
Original Message
From: Vesa-Matti Puro [
This email address is being protected from spambots. You need JavaScript enabled to view it.]
Sent: den 18 december 2002 12:11
To:
This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: Re: Testing
Hello!
The 3G UE conformance tests are specified in TTCN-2, you are right.
I guess that is what is standardized by ETSI/3GPP.
There is nothing prohibiting the development of Interoperability
and other types of tests using TTCN as well, but this maybe done
by individual companies as it may not be topic of standardized testing.
Development of Interoperability and other in-house tests using
TTCN would allow the re-use of the 3G test definitions (messages,
constraints/templates) etc in these types of tests as well. Using modular
TTCN, you can develop these tests as separate modules.
Then if you would like to use TTCN-3 to develop these types of
Interoperability and Fiedd tests, you could specify
'import from 3g_ue_test_module language "TTCN-2" all'
statement in your TTCN-3 module.
In this way, you would use existing 3G UE tests as TTCN-2 without
complex translation and you would be able develop your new tests
using TTCN-3. More details of this issue:
www.openttcn.com/Publications/Migration/
Vesa-Matti
> We know that TTCN is used for the test cases for the conformance tests
> as
> per 34.123
> Is TTCN also used for Interoperability and Field tests?
> What is the coverage of each of these tests.
> Where can I find the test specifications/GCF regulation for Field
> tests?
>
> Thanks and Regards,
> Jigna Shah
>
--
Vesa-Matti Puro
Open Environment Software Oy
Laserkatu 6, FIN-53850 LAPPEENRANTA, Finland
Postal address: P.O. Box 6, FIN-53851 LAPPEENRANTA, Finland
Telephone +358 40 820 4616
E-mail
This email address is being protected from spambots. You need JavaScript enabled to view it.
Web
www.openttcn.com 
