1 / 6

Status of STF 370 Automated Testing in February

This update provides an overview of the STF 370 Automated Testing project, including the outcomes of the preparatory meeting, the experts involved, the progress made so far, and the roadmap for the future.

allardb
Download Presentation

Status of STF 370 Automated Testing in February

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. Status of STF 370Automated Testingin February Stephan Schulz STF Leader

  2. Preparatory Meeting Outcome • 12 experts invited (and accepted) out of 22 applications • Very high profile of all applications • Decision to focus on TTCN-3 based test automation • Only one paid expert per company • Second expert ok if all their contribution is voluntary • Drafted first session plan for now for 2009 • WP1 – Methodology by May • Review of approaches for auto IOT in different domains • Development of one common application independent approach • WP2 – IMS architecture, TTCN-3, codec, adapter (all in parallel) by August, and then IMS Plugtest Report by November • Implementation of test system based on methodology for IMS Plugtest • WP3 – White paper and training material by early next year • Dissemination of experiences during project

  3. STF Team • External experts with area of special expertise • Olaf Bergengruen (R&S) - mobile networks, TTCN-3 • Luca Serazio (TI) - IMS • Anthony Baire (IRISA) – IETF, IPv6 Logo, Test System • Thomas Rings (University of Goettingen) – Grid computing • Yann Garci & Francois Fischer (FSCOM) – WiMax, B2B, Test System • Tuncay Namli (University of Ankara) – B2B • Bostjan Pintar (Sintesio) – IMS, TTCN-3 • Patrick Poglitsch, Theofanis Vassiliou-Gioles (TT) – IMS, TTCN-3, Test System • Tomas Urban (Elvior) – TTCN-3, Test System • Alexandre Berge (AMB) – WiMax, Test System • CTI expert contribution • Stephan Schulz (STF Leader) – IMS, Grid, HDMI, TTCN-3, Test System • Peter Kremer – WiMax, RFID, ROHC, TTCN-3 , Test System • Sebastian Mueller – EuroCAE, WiMedia, Smart Card, IPv6, TTCN-3

  4. Results so far • First session on methodology currently ongoing • Review of understanding of IOP and IOT in different domains • IMS, mobile networks, IETF, IPv6 Forum, ROHC, WiMax, VoIP in air traffic control, WiMedia, Smart Card, B2B applications, grid computing, RFID, HDMI • Also internal testing at operator, test system vendor, and ETSI • Start on drafting a methodology document • Key agreed terminology for automated interoperability testing • Major concepts, e.g., IOP, IOT, verdicts, results, level of automation, etc • A process for dealing with interoperability testing in specification development • Test design • Required content of interoperability test descriptions • Generic test architecture and desired characteristics

  5. Results of first work week • Collection and review of different existing methodologies related to interoperability testing • ETSI IOT, ETSI IPT, ETSI NIT, ETSI UMTS, Ericsson ROHC, INRIA IPv6, B2B, WiMax • Created and completed questionnaire on interpretation of interoperability and interoperability testing in different domains • Started work on methodology document • At times struggle to align or integrate with MTS IOT EG • Focus is on automation • Discovered some inconsistencies in document • Feedback will be collected and supplied to MTS • First RAW draft of methodology document is available for review • May also be up for discussion to move certain part to MTS IOT EG

  6. Road ahead • Finish general automated IOT methodology draft by May • Start of SIP IMS codec design & implementation in April • Start of design and documentation of IMS specific test architecture in end of April • Start of IMS TTCN-3 implementation in June • Based on input from TC INT test specification and scoping work • Start of adapter implementation in July • First integration and validation of IMS test system end of July • Potentially further development of IMS test system in September • At this point no fixed plan yet • Use of IMS test system as part of TC INT plugtest in mid October • Write experience report after event • Start capturing of experiences in white paper and training material in November

More Related