1 / 5

Some adDitional LangUage Features – input to the TDL Discussion

Some adDitional LangUage Features – input to the TDL Discussion. Gy Ö rgy R éthy Ericsson Test Competence Center. Requirements to TDL. MTS(11)0068 and MTS(12)TDL001 provide good input to the TDL discussion

braden
Download Presentation

Some adDitional LangUage Features – input to the TDL Discussion

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Some adDitional LangUage Features – input to the TDL Discussion GyÖrgy Réthy Ericsson Test Competence Center

  2. Requirements to TDL • MTS(11)0068 and MTS(12)TDL001 provide good input to the TDL discussion • MTS(12)TDL002 contains the essential requirements from Ericsson’s point of view to TDL (was input to the TDL#1 meeting, for info to this meeting) • While thebasic concept in MTS(12)TDL001 is rational, some elements essential for testing in the telecom domain are missing, UML SD should be extended with them

  3. Requirements to TDL • Elements to be added • TTCN-3 alt-like block is currently missing, the CSP/UML SD alt blocks has a different semantics; also the names of blocks shall be aligned with the already defined TTCN-3 operation names • unexpected event handling (defaults, also outcome of the TDL#1 meeting) • test cases shall be able to handle also unexpected events, not only the expected behaviour; this is essential for automated testing; as in most cases • default attachment (activation/deactivation) • the user shall be able to define points where he/she attaches/detaches one or or more defaults to the expected behaviour

  4. Requirements to TDL • Elements to be added (contd.) • verdict assignment • while it seems to be implicitly consented that the expected behaviour doesn’t need setting a verdict (always results pass), there are different kinds of unexpected behaviour: e.g. typically no response results an inconc verdict while an incorrect response results a fail verdict • timer expiration • needed in defaults, TTCN-3 alt-like blocks, provocative (negative) test cases etc. • delay • In some cases it is required to add defined delays between messages sent from the same or from different lifelines (e.g. slow underlaying transport layer on one of the interfaces, provocative test cases etc.) • interleave • In some interfaces TTCN-3 interleave is intensively used; adding an interleave block to TDL will decrease the complexity of TDL charts

More Related