1. TPLan A Notation for Expressing Test Purposes Version 2
43TD33
Anthony Wiles & Steve Randall
TC-MTS #43
Sophia Antipolis
October 2006

2. Main Objectives of TPLan v2
More flexible notation
User able to specify the “language” to suit application and project environment
Broader area of applicability
Not limited to IPv6 testing
Not even limited to communicating systems testing
30-May-19
MTS#43 TPLan

3. What remains from v1? Basic structure
TP Header
Followed by TP Body:
With {}
Ensure that {
when {…}
then {…} }
Fundamental communications keywords
IUT, Tester, receives, sends, …etc.
30-May-19
MTS#43 TPLan

4. What’s New in v2? Keyword set reduced to bare minimum
User able to provide cross-references for
Requirements sources
Configurations
User able to define:
New keywords
Entities
Events (messages) with parameters
Values
Conditions (states)
User able to specify syntactical context of new words
Ordering
Logical
Temporal
30-May-19
MTS#43 TPLan

5. Reduced Keyword Repertoire (1)
Header
title date summary etc.
Structural
with when then group etc.
Communications testing
IUT sends receives etc.
Direction
from to
Data related
containing indicating
Logical
and or not
30-May-19
MTS#43 TPLan

6. Reduced Keyword Repertoire (1)
Definitions
def word value event etc.
Cross-reference
xref
Condition
state
Timer-related
before during after
“Glue” words
a an the is etc.
30-May-19
MTS#43 TPLan

7. Cross References Cross-reference to requirements sources
xref RQ_002 {RFC4301, RFC4302,
RFC4305, RFC4306}
Cross-reference to configurations
xref CF_SEC_01 {Configs_IOP_SEC.pdf}
xref CF_SEC_02 {Configs_IOP_SEC.pdf}
30-May-19
MTS#43 TPLan

8. Definitions (1) Entities def entity EUT def entity QE1 Events
def event packet {Authentication_Header, source_address, destination_address, sequence_number }
def event restart_timer {5 seconds}
30-May-19
MTS#43 TPLan

9. Definitions (2) Values def value lifetime def value seconds Keywords
def word requested def word indicates def word receipt
Syntactical context
def context {is [not] ~requested to } def context {~indicates ~receipt } def context {~indicates [the] ~lifetime }
30-May-19
MTS#43 TPLan

10. Ordering Logical Ordering (Precedence) Temporal Ordering
with { IUT established in a binding to Home_Agent and ( IUT in busy state or IUT in alerting state) }
Temporal Ordering
when { IUT receives SETUP before Timer_14 expires }
when { not ordered ( IUT receives SETUP and Timer_14 expires ) }
Note: Default is “ordered”
30-May-19
MTS#43 TPLan

11. Conclusion TPLan V2 is: TPLan V2 should:
more flexible and versatile that V1
aimed at testing in general rather than just communications protocols
TPLan V2 should:
provide a framework for consistent TP development
be considered to be complementary to TTCN-3
integrate well with TTCN-3 tools
TPLan V2 has been used extensively and successfully in Phase-2 of the IPv6 testing project using only limited tool support
TPLan is presented for MTS approval as ES
30-May-19
MTS#43 TPLan

12. TPLan A Notation for Expressing Test Purposes Version 2