ETSI TR 103 386-2016 Methods for Testing and Specification (MTS) Deployment of Model-Based Automated Testing Infrastructure in a Cloud (V1 1 1)《测试和规范方法(MTS) 在云端部署基于模型的自动化测试基础设施(V1 .pdf

《ETSI TR 103 386-2016 Methods for Testing and Specification (MTS) Deployment of Model-Based Automated Testing Infrastructure in a Cloud (V1 1 1)《测试和规范方法(MTS) 在云端部署基于模型的自动化测试基础设施(V1 .pdf》由会员分享，可在线阅读，更多相关《ETSI TR 103 386-2016 Methods for Testing and Specification (MTS) Deployment of Model-Based Automated Testing Infrastructure in a Cloud (V1 1 1)《测试和规范方法(MTS) 在云端部署基于模型的自动化测试基础设施(V1 .pdf（87页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 103 386 V1.1.1 (2016-04) Methods for Testing and Specification (MTS); Deployment of Model-Based Automated Testing Infrastructure in a Cloud TECHNICAL REPORT ETSI ETSI TR 103 386 V1.1.1 (2016-04) 2 Reference DTR/MTS-103386 Keywords cloud, testing ETSI 650 Route des Lucioles F-06921 Sophia An

2、tipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present

3、 document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions

4、 and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the curre

5、nt status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No par

6、t may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the forego

7、ing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the be

8、nefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 103 386 V1.1.1 (2016-04) 3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Nor

9、mative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 11g34 An integrated framework for testing automation on a cloud infrastructure . 13g34.0 Overview of the approach 13g34.1 Roles, relationships and interactions among TaaS

10、users 13g34.2 End user services 15g35 End user use cases 16g35.0 Considered end user use cases 16g35.1 Direct test execution use case . 17g35.1.0 Description 17g35.1.1 Direct test execution use case TaaS sequence diagram. 17g35.2 Manual test design use case 20g35.2.0 Description 20g35.2.1 Manual tes

11、t design use case TaaS sequence diagram . 22g35.3 Automated test design use case 23g35.3.0 Description 23g35.3.1 Automated test design use case TaaS sequence diagram 24g36 Representation of System models in TPaaS . 25g36.0 Approaches to formal test descriptions 25g36.1 MDSL conceptual model 26g36.1.

12、0 Introduction. 26g36.1.1 Test Planning Concept 26g36.1.2 Test Analysis Concepts . 27g36.1.3 Test Design Concepts . 29g36.1.4 Test Case Concepts . 29g36.1.5 Test Data Concepts . 30g36.1.6 Test Derivation Concepts 31g36.1.7 Refined Test Design Concepts 33g36.1.8 Test Scheduling Concepts . 34g36.2 Rea

13、lisation as UML Profiles 35g36.2.0 Introduction. 35g36.2.1 Test Planning Concepts Implementation 36g36.2.2 Test Requirement Implementation 36g36.2.3 Test Object Implementation 36g36.2.4 Test Component Implementation 36g36.2.5 SUT Implementation. 36g36.2.6 Test Configuration Implementation 37g36.2.7

14、Test Case Implementation 37g36.2.8 Precondition Implementation 37g36.2.9 Postcondition Implementation 37g36.2.10 Parameter Implementation 37g36.2.11 Stimulus Implementation 37g36.2.12 Response Implementation . 37g36.2.13 Verdict Implementation 37g36.2.14 Test Design Model Implementation 37g36.2.15 T

15、estData Implementation 37g3ETSI ETSI TR 103 386 V1.1.1 (2016-04) 4 6.2.16 DataPartition Implementation . 38g36.2.17 TestDataValue Implementation 38g36.2.18 DataPool Implementation . 38g36.2.19 Test Suite Implementation 38g36.2.20 Test Procedure Implementation 38g36.2.21 Scheduling Specification Impl

16、ementation 38g36.3 Constraints on the MIDAS DSL . 39g36.3.0 Introduction. 39g36.3.1 TestConfiguration/TestContext Constraints . 39g36.3.2 TestCase Constraints. 39g36.3.3 TestProcedure Constraints 42g36.4 MDSL Validator . 42g36.5 TTCN-3 Generator . 43g36.6 SCA4SAUT approach to system modelling . 44g3

17、6.6.0 Introduction. 44g36.6.1 Overview of the SCA4SAUT model 45g36.6.2 Introduction to the SCA Assembly notation . 46g37 Deployment of the TPaaS on the public cloud infrastructure 49g37.0 Development and production frameworks . 49g37.1 Integration of test methods on the TPaaS platform 49g37.1.0 Intr

18、oduction. 49g37.1.1 The Database structure for the MIDAS TPaaS . 50g37.1.2 The storage file system for MIDAS TPaaS 52g37.2 Implemented facilities 52g37.2.1 Development Environment (devenv_vm) . 52g37.2.2 Production Environment (prodenv_multivm) . 53g3Annex A: End User Use Case Examples 56g3A.1 Direc

19、t Execution Use Case Example: IMS Conformance testing 56g3A.1.0 Overview 56g3A.1.1 IMS as SUT 56g3A.1.2 Test configuration. 57g3A.1.2.1 SUT architecture . 57g3A.1.2.2 Message flow scenarios 58g3A.1.2.3 Test suite structure 59g3A.1.3 Direct execution procedures taken within TPaaS . 59g3A.1.4 Lesson l

20、earned from direct execution use case . 61g3A.2 Manual test design example - SCM Pilot . 62g3A.2.0 Overview 62g3A.2.1 SCM Pilot . 62g3A.2.2 Test configuration. 65g3A.2.3 Message flow scenarios 70g3A.2.4 Manual execution . 74g3A.2.5 Experiences 75g3A.3 Automated test design example - e-Health Pilot 7

21、7g3A.3.0 Overview 77g3A.3.1 e-Health Pilot 77g3A.3.2 Test configuration. 79g3A.3.3 Message flow scenarios 82g3A.3.4 Automated execution 84g3A.3.5 Experiences 85g3History 87g3ETSI ETSI TR 103 386 V1.1.1 (2016-04) 5 Intellectual Property Rights IPRs essential or potentially essential to the present do

22、cument may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect

23、of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of othe

24、r IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). Modal verbs terminol

25、ogy In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ET

26、SI deliverables except when used in direct citation. ETSI ETSI TR 103 386 V1.1.1 (2016-04) 6 1 Scope The present document provides an overview of the approach taken within the EU-funded research project called MIDAS to design, build and deploy an integrated framework for testing automation that will

27、 be available as a Test as a Service (TaaS) on a Cloud infrastructure, and which covers key testing activities: test suite generation, test execution, scheduling, evaluation and test results arbitration. While MIDAS is focused on the test automation for Service Oriented Architecture (SOA), the testi

28、ng methods and technologies that are investigated and prototyped within the project can be generalized to a greater degree and can be applied not only to SOA System Under Test (SUT), but also to SUTs in other domains, e.g. Automotive, Telecommunications, Machine-to-Machine services. Such broader app

29、lication relates particularly to model-based test design and test suite generation, model checking of choreographies for sound interaction of test scenarios, fuzzing for security testing, usage-based testing, probabilistic inference reasoning for test evaluation and scheduling. 2 References 2.1 Norm

30、ative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments)

31、applies. Referenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The follo

32、wing referenced documents are necessary for the application of the present document. Not applicable. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version

33、applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not

34、 necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI ES 202 951: “Methods for Testing and Specification (MTS); Model-Based Testing (MBT); Requirements for Modelling Notations“. i.2 ETSI ES 203 119: “Methods for Testing and

35、 Specification (MTS); The Test Description Language (TDL); Specification of the Abstract Syntax and Associated Semantics“. i.3 MIDAS Deliverable D6.1.WP6 (2014): “Analysis of required functionalities and available public Cloud services“. i.4 MIDAS Deliverable D6.3.WP6 (2014): “The basic MIDAS platfo

36、rm and the integrated test evaluation, planning and scheduling macro-component“. i.5 ISO/IEC 9126-1 (2001): “Software engineering - Product quality“. i.6 ISO 9001 (2005): “Quality Management Systems - Requirements“. i.7 ISO/IEC/IEEE 29119: “Software Testing Standard“. NOTE: Available at http:/www.so

37、ftwaretestingstandard.org. ETSI ETSI TR 103 386 V1.1.1 (2016-04) 7 i.8 UTP-1-2 (2013). UML testing profile (UTP) version 1.2. Tech. Rep. formal/2013-04-03, Object Management Group. i.9 International Software Testing Qualifications Board (ISTQB): ISTQB/GTB standard glossary for testing terms. NOTE: A

38、vailable at http:/www.istqb.org/downloads/send/40-glossary-archive/180-istqb-glossary-of-testing-terms.html. i.10 Object Management Group (OMG): Business Motivation Model (BMM). NOTE: Available at http:/www.omg.org/spec/BMM. i.11 IEEE 610.12 (1990): “IEEE Standard Glossary of Software Engineering Te

39、rminology“. i.12 MIDAS Deliverable D2.1 (2013): “Requirements for automatically testable services and services architectures“. i.13 ETSI TS 102 790-1: “Core Network and Interoperability Testing (INT); IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Confo

40、rmance Testing; (3GPP Release 10); Part 1: Protocol Implementation Conformance Statement (PICS)“. i.14 ETSI TS 102 790-2: “Core Network and Interoperability Testing (INT); IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; (3GPP Release

41、 10); Part 2: Test Suite Structure (TSS) and Test Purposes (TP)“. i.15 ETSI TS 102 790-3: “Core Network and Interoperability Testing (INT); IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; (3GPP Release 10); Part 3: Abstract Test Suit

42、e (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification“. i.16 ETSI TS 123 228: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228)“. i

43、.17 ETSI TS 124 229: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229)“. i.18 SCA-AM-V1-0 (200

44、7). Service component architecture assembly model specification version 1.0. Tech. rep., OSOA. i.19 SCA-AM-V1-1 (2011). Service component architecture assembly model specification version 1.1. Tech. Rep. OASIS Committee Specification Draft 09 / Public Review Draft 04, OASIS. i.20 SoaML-1-0-1 (2012).

45、 Service Oriented Architecture Modeling Language (SoaML) Specification, Version 1.0.1. formal-12-05-10. Object Management Group. i.21 SOAP-1-1 (2000). Simple object access protocol (SOAP) 1.1. Tech. Rep. W3C Note 08 May 2000, World Wide Web Consortium. i.22 WSDL-1-1 (2001). Web service definition la

46、nguage (WSDL) 1.1. Tech. Rep. W3C Note 15 March 2001, World Wide Web Consortium. i.23 XML-Infoset (2004). XML information set (second edition). Tech. Rep. W3C Recommendation 4 February 2004, World Wide Web Consortium. i.24 XPath-2-0 (2010). XML path language (XPath) 2.0 (second edition). Tech. rep.,

47、 World Wide Web Consortium. W3C Recommendation 14 December 2010, World Wide Web Consortium. i.25 XSD-1-Structures (2004). XML schema part 1: Structures second edition. Tech. Rep. W3C Recommendation 28 October 2004, World Wide Web Consortium. i.26 MIDAS Deliverable (2014): “SAUT Construction Model Sp

48、ecification Service Component Architecture for Services Architecture Under Test (SCA4SAUT) - V. 1.2“. ETSI ETSI TR 103 386 V1.1.1 (2016-04) 8 i.27 IEEE 829: “IEEE Standard for Software and System Test Documentation“. i.28 ETSI TR 102 840: “Methods for Testing and Specifications (MTS); Model-based te

49、sting in standardisation“. i.29 ETSI ES 201 873 (all parts): “Methods for Testing and Specification (MTS) The Testing and Test Control Notation version 3“. i.30 ISO/IEC 9646-1: “Information Technology - Open Systems Interconnection - Conformance testing methodology - Part 1: General concepts“. i.31 ISO 28000: “Specification for security management systems for the supply chain“. i.32 ISO 9000: “Quality management systems - Fundamentals and vocabulary“. i.33 Supply Chain Operations Reference model (