1. Typical Workflow - today
Ericsson input to MTS's TDL meeting
Typical Workflow - today
GUI support
Code development support
editors, static code checking, build support
Test execution (TC, control part, test sets)
Log analysis
support
GUI level
Test cases (Fwk user)
Runtime
configuration
pETS
logs
Test framework (SW library)
ETS
Code level
Centralized protocol support (adapters, type modules, message encdec
Titan
Ericsson AB 2011

2. The most often heard sentence from users (MANAGERS VIEW)
OUR TESTERS SHALL SPEND TIME ON TESTING THE
> SUT <
AND NOT ON “FIDDLING” WITH THE TTCN-3 CODE

3. Ericsson input to MTS's TDL meeting
Raise the Abstraction Level: case 1 Graphical test case and data handling
Example Test data editor view
Example TDL view borrowed from TD MTS(11)0068
Graphical Test Data Editor
Graphical TDL Editor
TTCN template generator engine
TTCN code generator engine
Log analysis support
Code development
support
Test execution
other GUI utilities
TTCN-3 code generation: open API
Test framework (SW library)
Generated TTCN-3 code
Ericsson AB 2011

4. Raise the Abstraction Level: case 2 Adapt to the MBT Paradigm
Ericsson input to MTS's TDL meeting
Raise the Abstraction Level: case 2 Adapt to the MBT Paradigm
Model Editor and test case generator
TDL generation and data exchange
Graphical Test Data Editor
Graphical TDL Editor
TTCN template generator
TTCN code generator engine
Log analysis support
Code development
support
Test execution
other GUI utilities
TTCN-3 code generation: open API
Test harness (SW library)
Generated TTCN-3 code
Ericsson AB 2011

5. Log viewing – example
not comp. creation but existence of the interface
Common elements of test description and test log presentation

6. Feedback from logs to test description
Ericsson input to MTS's TDL meeting
Feedback from logs to test description
Creating new test cases from the logs of existing ones
(in addition to creating them manually or generating them by an MBT tool)
GUI level
MBT tool
TDL
support
Code development
support
Test execution
other utilities
Log analysis support
GUI level
Generated test cases
Runtime
configuration
pETS
logs
Code level
ETS
Test framework (SW library)
Ericsson AB 2011

7. Requirements to TDL
Shall be on a higher abstraction level as the TTCN-3 code
only events and data important for the tester shall be shown
Shall be intuitive – no learning curve “at all”
Shall present test cases from the point of view of the SUT
Mapping of SUT interfaces to TTCN-3 components should be handled at the lower (test harness) level
Test data: relevant part to be handled in TDL/model level
Only part of the messages (specific IEs, headers etc.) that makes difference in the behaviour – but ONLY that part of the data
TDL shall support both test definition (MBT & manual) and log presentation
these are partly overlapping sets of graphical elements
Elements (to be discussed and specified in this work item)
available: timer, alt, …
additional: setverdict, …