1 / 9

39TD07 STF256 – IPv6 Test Methodology

39TD07 STF256 – IPv6 Test Methodology. MTS#39 Sophia Antipolis 20-21 October. TS 102 351 v1.1.1 Main Contents. Test Development Process Conformance and Interoperability Requirements Catalogue TPs and Test Purpose Language Conformance test suites (TTCN-3)

meira
Download Presentation

39TD07 STF256 – IPv6 Test Methodology

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. 39TD07STF256 – IPv6 Test Methodology MTS#39 Sophia Antipolis 20-21 October

  2. TS 102 351 v1.1.1 Main Contents • Test Development Process • Conformance and Interoperability • Requirements Catalogue • TPs and Test Purpose Language • Conformance test suites (TTCN-3) • Interoperability test descriptions • TTCN-3 Library • Structure • Elements of library • Adding modules to the library • Specifying upper testers • Naming conventions • General naming conventions • TTCN-3 naming conventions

  3. TTCN-3 Library IPv6 Test Development Process (1) RFC + 3GPP + Industry Practice etc Requirements Catalogue interoperability conformance TSS&TP Test Description Test Suite (TTCN-3) TSS&TP Test Suite (TTCN-3)

  4. IPv6 Test Development Process (2) RFC1..RFCn+3GPP+Industry Practice etc One or More Requirements One or More TPs {One or More TP Functions} One or More TCs {One or More TC Functions}

  5. Naming (1) Area (Core, IPSec, Mobility ...) RQ_01_001 TP_01_001_01..99 {f_TP_01_001_01_PTC1..PTCk} One or More TCs {f_TC_01_001_01_PTC1..PTCk} Requirement number (1-999) TP range number 91-99) Architectural Role (host, router ...)

  6. Naming (2) • TP groups, TPs and TCs will have ‘cryptic’ identifiers for machine processing (linking) • TP_01_001_01 • And explanatory titles for readability • aligning PadN option

  7. Naming (3)

  8. Test Purposes (TP Lan) tp id TP_01_001_01 title aligning PadN option rc ref RC_61255 config ref CF_01 ensure that when { IUT receives Echo Request from TN1 containing Hop-by-Hop Options Header indicating Header Ext Length field ZERO and PadN option containing Opt Data Len field set to 4 and Option Data aligning the Hop-by-Hop Options Header to a multiple of 8 octets } then { IUT sends Echo Request to TN2} BNF will be developed in Edition 2 (STF 276)

  9. Presentation and Tools • The methodology does not prescribe formats, but ... • STF 276 will go for hypertexted documentation • => web-based presentation • Requirements Catalogue in HTML • linked to base RFCs etc. • TPs in TPLan (text) • linked to RC • TTCN-3 in core language (text) • will use TTCN-3 doc to link to TPs and RC (by tags) • TTCN-3 doc tags will be defined in STF276 (like JavaDoc) • Need tool support • will be provided by voluntary contribution • Federico Engler (Farodyne Solutions)

More Related