100 likes | 195 Views
Testing activities in the @rmor project. INRIA 1B Evaluation 23 October 2003. César VIHO. Why, how and who ?. Interoperability is the final goal of any product developed in communicating systems area
E N D
Testing activities in the @rmor project INRIA 1B Evaluation 23 October 2003 César VIHO
Why, how and who ? • Interoperability is the final goal of any product developed in communicating systems area • Bringing testing expertise into the existing design and development expertise of @rmor to : • Increase confidence on developed component • Validate and improve the methodologies to be developed in both testing and design parts (i.e. “tests are used to test components and components are used to test the tests”) • Testing activities started in 2000 (one year after the creation of @rmor) Participants :C. Viho, R. Marie, L. Toutain, F. Dupont, D. Ros F. Roudaut, S. Barbin, F. Ngani, L. Tanguy, H. Leguen A. Minaburo, O. Medina, V. Phi
The context of testing activities Specifications/Standards vendor B vendor A Design and Development methodology B Conformance testing Implementation A Implementation B Interoperability testing
@rmor covers all steps of testing Specification • Generation of Abstract Test Suite(ATS) • Compilationof ATS into Executable Test Suite(ETS) • Executionof ETS against the Implementation Under Test (IUT) • Test results Analysis ATS ETS Verdict/log
Theoretical aspects and results (1) • Formal approach for : • Conformance and interoperability testing of communication networks and protocols, • Test selection and test coverage measurement • Models used : • IOLTS (Input-Output labeled transition systems) • Labeled Markov chains
Theoretical aspects and results (2) • Formal approach for interoperability testing : • Definition and classification of interoperability testing architectures • First formal definition of the notion of interoperability • Formally proved answers to FAQs • Two solutions for distributed testing
IPv6 related testing • Test suites developed (both conformance and interoperability) : • Core protocols (Neighbor Discovery, PMTU discovery, etc) • Mobile IPv6 (Correspondent Node, Home Agent, Mobile Node) ID-13, ID-15, ID-18 and ID-19 • Routing protocols (RIPng, OSPFv3) • PPPv6 • Transition Mechanisms (6to4, ISATAP, SIIT/NAT-PT) • Header Compression mechanisms (ROHC) • Tight collaborationwith theTAHI project in Japan
Organization of IPv6 interoperability testing events • In tight collaboration with the ETSI (European Telecommunication Standardization Institute) PlugtestsTM Service • Test expertise provided for : • The 4 IPv6 interoperability events organized by the ETSI (Sophia’2000, Cannes’2001 and 2002, Brussels’2003) • Two Japanese TAHI IPv6 interoperability events (Yokohama’2002 and Chiba’2003) • The @rmor project is now well-known and recognized as an expert group in IPv6 testing
The IPv6 certification programme “IPv6 Ready Logo” • A world-wide certification programme for IPv6 related products launched by the IPv6 Forum, ETSI and IRISA/Armor project • Based on interoperability testing results • IRISA/Armor is responsible of : • The definition of technical requirements for the two phases of the programme • The operational (applications examination and approval decision) for European applications • With our visibility today…
Next 4 years T1 T2 T3 IUT1 IUT2 IUT3 • Defining a formal framework and distributed approach for interoperability testing (continuing) • Precise definition(s) of interoperability • Test generation from formal specifications • (Remote) testing platform and environment (using ISO/IS 9646, TTCN.v3 language) • Test generation for IPv6-related protocols and corresponding standardization and certification activities (continuing) • Towards Mobile Network Testing (gathering experience from MIPv6 testing) • Security testing combined with conformance and interoperability testing (test composition) • Test coverage (labeled Markov chains)