TTCN-3核心语言手册：v4.11.1英文版

需积分: 9 84 浏览量更新于2024-07-15 收藏 1.62MB PDF 举报

"Core Language_v4.11.1.pdf 是一份关于TTCN-3核心语言的文档，属于ETSIES201873-1V4.11.1标准，由欧洲电信标准协会(ETSI)发布。这份资料是英文版，关键词包括语言、方法论、测试和TTCN-3。TTCN-3全称为Testing and Test Control Notation version 3，是一种专门用于测试和规格说明的方法。" TTCN-3（Tester Testing and Test Control Notation version 3）是国际上广泛使用的通信系统和软件系统的测试语言，它是一种强大的、形式化的、基于文本的测试语言。TTCN-3的核心语言部分包含了进行系统测试所需的各种语法和结构，使得测试人员可以编写出精确、可读性强的测试用例。在TTCN-3中，你可以找到以下关键知识点： 1. **语法规则**：TTCN-3具有严谨的语法结构，包括数据类型、变量、常量、表达式、控制结构（如循环、条件语句）、函数和模块等。这些元素允许测试工程师构造复杂的测试场景。 2. **数据类型**：TTCN-3支持多种数据类型，如基本类型（如整型、浮点型、字符串等）、复合类型（如数组、记录、枚举）以及用户自定义类型。 3. **模块化设计**：TTCN-3鼓励使用模块化的编程方式，通过导入和导出来组织代码，提高代码复用性和可维护性。 4. **测试操作**：TTCN-3提供了一套丰富的测试操作，如发送和接收消息、断言（检查测试条件是否满足）、计时器（用于控制测试流程的时间）等。 5. **事件处理**：TTCN-3支持异步事件模型，可以处理系统中的并发和同步问题。 6. **测试用例管理**：TTCN-3允许定义测试用例集合和测试用例执行顺序，便于管理和执行大规模的测试计划。 7. **编译与执行**：TTCN-3代码需要通过编译器转化为可执行的测试程序，这些程序可以在不同的平台上运行，支持跨平台测试。 8. **接口和适配器**：TTCN-3允许定义和实现与被测系统交互的接口和适配器，以便于连接和控制各种系统。 9. **错误处理**：TTCN-3提供了强大的错误处理机制，包括错误声明、异常处理和报告，帮助调试和定位测试过程中出现的问题。 10. **测试结果评估**：测试执行后，TTCN-3可以生成详细的测试报告，包括成功和失败的测试用例，以及测试覆盖率等信息。由于TTCN-3的标准化和通用性，它在电信、网络、软件工程等领域有着广泛应用。学习TTCN-3对于测试工程师来说，意味着掌握了高效、精确的系统测试工具。不过，由于提供的资源是英文版，可能需要具备一定的英文阅读能力。如果能找到中文版的资料，对于中文使用者来说将更便于理解和学习。

ETSI

ETSI ES 201 873

1 V4.11.1 (2019

04)

[i.20] ETSI ES 201 873-1 (V3.2.1): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2007.

[i.21] ETSI ES 201 873-1 (V3.3.2): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2008.

[i.22] ETSI ES 201 873-1 (V3.4.1): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2008.

[i.23] ETSI ES 201 873-1 (V4.1.1): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2009.

[i.24] ETSI ES 201 873-1 (V4.2.1): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2010.

[i.25] ETSI ES 201 873-1 (V4.3.1): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2011.

[i.26] ETSI ES 201 873-1 (V4.4.1): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2012.

[i.27] ETSI ES 201 873-1 (V4.5.1): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2013.

[i.28] ETSI ES 201 873-1 (V4.6.1): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2014.

[i.29] ETSI ES 201 873-1 (V4.7.1): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2015.

[i.30] ETSI ES 201 873-1 (V4.8.1): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2016.

[i.31] ETSI ES 201 873-1 (V4.9.1): "Methods for Testing and Specification (MTS); The Testing and

Test Control Notation version 3; Part 1: TTCN-3 Core Language", 2017.

3 Definition of terms, symbols and abbreviations

3.1 Terms

For the purposes of the present document, the terms given in Recommendation ITU-T X.290 [5], Recommendation

ITU-T X.292 [3] and the following apply:

actual parameter: value, expression, template or name reference (identifier) to be passed as parameter to the invoked

entity (function, test case, altstep, etc.) as defined at the place of invoking

assignment notation: notation that can be used for record, set, record of and set of values, where the fields or the

elements to which a value is assigned are identified explicitly within a pair of curly brackets ("{" and "}") by the field

names or the positions of the elements

basic types: set of predefined TTCN-3 types described in clauses 6.1.0 and 6.1.1 of the present document

NOTE: Basic types are referenced by their names.

behaviour definition: dynamic test behaviour, which is either a testcase, a function, or an altstep definition

communication port: abstract mechanism facilitating communication between test components

NOTE: A communication port is modelled as a FIFO queue in the receiving direction. Ports can be

message-based or procedure-based.

ETSI

ETSI ES 201 873

1 V4.11.1 (2019

04)

compatible type: TTCN-3 is not strongly typed but the language does require type compatibility

NOTE: Variables, constants, templates, etc. have compatible types if conditions in clause 6.3 are met.

completely initialized: Value or template is completely initialized if it is not uninitialized and, if its type is a structured

type, all its required parts are completely initialized. Additionally, templates are completely initialized if they are

assigned a matching mechanism all parts of which are completely initialized. If a value or template is completely

initialized, it fulfils the requirement of being "at least partially initialized".

NOTE: A value or template of a simple, component or default type is completely initialized if anything but

the unchanged symbol "-" has been assigned to it.

A value or template of a union or anytype type is completely initialized if one of its variants has been

completely initialized.

A value or template of a record or set type with only optional fields and the optional

"implicit omit" attribute attached, is completely initialized if the value "{}" is assigned, as all

fields are implicitly set to omit.

A value or template of a record or set type with no fields is completely initialized with assignment of

the value "{}".

A value or template of a record of, set of or array type is completely initialized if at least the first n

elements are completely initialized, where n is the minimal length imposed by the type length restriction

or array definition. Thus in case of n equals 0, the assignment of the value "{}" also completely initializes

such a record of, set of or array.

component constant: constant defined in a component type

component port: port defined in a component type

component template: template defined in a component type

component timer: timer defined in a component type

component variable: variable defined in a component type

control behaviour: Functions and altsteps that are used for the dynamic execution of test cases are called control

behaviour. They are called control functions and control altsteps respectively. Module control functions have the name

control and can be used as an entry point of executing a test suite. Other control behaviour definitions are those that are

called directly either by module control functions or from other control behaviour. Declaring functions or altsteps with

the modifier @control explicitly allows to distinguish them from test case behaviour definitions in their special role.

Module control functions and behaviour definitions with the @control modifier are called explicit control behaviour

definitions, i.e explicit control functions and explicit control altsteps.

data types: common name for simple basic types, basic string types, structured types, the special data type anytype and

all user defined types based on them

NOTE: See table 3 of the present document.

defined types (defined TTCN-3 types): set of all predefined TTCN-3 types (basic types, all structured types, the type

anytype, the address, port and component types and the default type) and all user-defined types declared either in the

module or imported from other TTCN-3 modules

deterministic function: function that for the same input in the in and inout parameters always yields the same output

both for the return result as well as the inout and out parameters

NOTE 1: A non-deterministic function is one that is not deterministic.

NOTE 2: In general, it cannot be decided if a function is deterministic or not. However, a function can be specified

to be deterministic, i.e. the function is supposed to be deterministic. In this case, a violation of the

determinism can be detected and handled accordingly. The handling however is tool-specific.

dynamic parameterization: form of parameterization, in which actual parameters are dependent on runtime events

EXAMPLE: The value of the actual parameter is a value received during runtime or depends on a received

value by a logical relation.

ETSI

ETSI ES 201 873

1 V4.11.1 (2019

04)

exception: in cases of procedure-based communication, an exception (if defined) is raised by an answering entity if it

cannot answer a remote procedure call with the normal expected response

formal parameter: typed name or typed template reference (identifier) not resolved at the time of the definition of an

entity (function, test case, altstep, etc.) but at the time of invoking it

NOTE: Actual values or templates (or their names) to be used at the place of formal parameters are passed from

the place of invoking the entity (see also the definition of actual parameter).

fuzzy value or template: If a value or template instance is declared to be fuzzy, the expression, initializing or partly

initializing it (including actual parameters passed to in formal parameters), is subject to lazy evaluation. During

execution, this expression is re-evaluated each time when the fuzzy object is referenced, except when at the left hand

side of an assignment or passing it to a fuzzy or lazy formal parameters. The result of this (re)evaluation is used as the

actual value or template of the fuzzy instance. When new content is assigned to a fuzzy instance or to its subpart, the

right hand side of the assignment is subject to lazy evaluation again.

global visibility: attribute of an entity (module parameter, constant, template, etc.) whose identifier can be referenced

anywhere within the module where it is defined including all functions, test cases and altsteps defined within the same

module

Implementation Conformance Statement (ICS): See Recommendation ITU-T X.290 [5].

Implementation eXtra Information for Testing (IXIT): See Recommendation ITU-T X.290 [5].

Implementation Under Test (IUT): See Recommendation ITU-T X.290 [5].

in parameterization: kind of parameterization where the value of the actual parameter (the argument) is assigned to the

formal parameter when the parameterized object is invoked, but the value of the formal parameter is not passed back to

the actual parameter when the invoked object completes

NOTE 1: In in parameterization, parameters are passed by value.

NOTE 2: The arguments are evaluated before the parameterized object is entered.

NOTE 3: Only the values of the arguments are passed and changes to the arguments within the invoked object have

no effect on the arguments as seen by the invoking object.

index notation: notation to access individual elements of record of, set of, array and string values or templates, where

the element to be accessed is identified explicitly by an index value enclosed in square brackets ("[" and "]") which

specifies the position of that element within the referenced value or template and the index value is either an integer

value, array of integers or record of integers

NOTE: Integer values used for indexing (either directly or as elements of the record of or array values) always lie

within the index range of the type of the referenced value or template. Except for those arrays which are

defined with an explicit index range, the index range always has 0 as the index for the first element.

initialization: value or template, or a value or template field is initialized when a content is first assigned to it

NOTE: The assignment may be explicit at the declaration of the given object, in which case the same restrictions

apply as for the right-hand side of the assignment operation, or at first use on the left-hand side of an

assignment, or may be implicit. Implicit initialization occurs when a yet uninitialized object is passed as

actual parameter to an out formal parameter of a directly called testcase, function or altstep returns with a

non-uninitialized value or template that is assigned to the actual parameter; or when module parameters

not initialized in the TTCN-3 code get their runtime values before test suite execution.

inout parameterization: kind of parameterization that uses passing by reference, i.e. when the parameterized object is

invoked, the formal parameter is linked with the actual parameter and gets direct access to the same data content that is

currently represented by the actual parameter

NOTE 1: The invoked object uses the actual parameter directly, so that all changes made in the formal parameter

become immediately effective on the actual parameter. If the same actual parameter is passed to two

distinct formal parameters, a change in one formal parameter becomes immediately effective in the other

one (and in the actual parameter).

ETSI

ETSI ES 201 873

1 V4.11.1 (2019

04)

NOTE 2: Inout parameters can be used for functions, altsteps, and test cases only, if not restricted by further rules,

e.g. altsteps activated as defaults.

known types: set of all TTCN-3 predefined types, types defined in a TTCN-3 module and types imported into that

module from other TTCN-3 modules or from non-TTCN-3 modules

lazy evaluation: Lazy evaluation means that evaluation of an expression is delayed during execution until the value or

template instance, to which the result of the evaluation should have been assigned or passed to as actual parameter, is

first referenced at another place than the left hand side of an assignment or an actual parameter passed to a fuzzy or lazy

formal parameter. During execution, this delayed evaluation is carried out at the first actual reference, even when the

result is to be used in an expression that is also subject to lazy evaluation. For the evaluation the actual values at the

time of the evaluation are to be used (not the actual values at the time of the assignment or parameter passing). This

implies that components of the expression may be uninitialized at the time, when execution reaches the assignment or

parameter passing, but may be initialized by the time of the evaluation that can lead to successful evaluation. If, by the

time of the evaluation, execution has left the scope unit, in which one or more components of the expression is defined,

the actual values of the component(s) at the time of leaving the scope unit are to be stored for the purpose of the delayed

evaluation (but only for that, i.e. the values are not accessible for the user).

lazy value or template: A value or template instance is called lazy, when the expression, initializing or partly

initializing it (including actual parameters passed to in formal parameters), is subject to lazy evaluation. When, during

execution, the delayed (lazy) evaluation is taking place, its result is stored in the lazy value or template and the lazy

instance is used further on like ordinary values and templates, until the next use of the lazy variable or parameter on the

left hand side of an assignment. When a new content is assigned to a lazy instance or to its subpart, the right hand side

of the assignment is subject to lazy evaluation again. If, during execution, no expression referencing the lazy object is

evaluated, the lazy value or template instance is never evaluated.

left hand side (of assignment): value or template variable identifier or a field name of a structured type value or

template variable (including array index if any), which stands left to an assignment symbol (:=)

NOTE: A constant, module parameter, timer, structured type field name or a template header (including template

type, name and formal parameter list) standing left of an assignment symbol (:=) in declarations and or a

modified template definitions are out of the scope of this definition as not being part of an assignment.

local visibility: attribute of an entity (constant, variable, etc.) that its identifier can be referenced only within the

function, test case or altstep where it is defined

Main Test Component (MTC): See Recommendation ITU-T X.292 [3].

object: instance of one of the object types (component, default, port and timer)

NOTE: Objects of type default, port or timer, which are owned by the component that instantiated them, are local

objects while objects of type component are global objects. Global objects can be referenced from other

component scopes while references to local objects can only be used by the component they are bound to.

object reference: special kind of value used for instances of component, default, port and timer types which represents

a reference to an existing entity in the TE

NOTE: When used in assignments or parameter passing, only the reference to the entity is copied, but not the

entity itself. An object reference can also be initialized with the special value null in which case it does

not reference an object.

out parameterization: kind of parameterization where the actual parameter's content (the argument) is not passed to

the formal parameter when the parameterized object is invoked, but the content of the formal parameter is passed back

to the actual parameter when the invoked object completes, if the formal parameter has been initialized during the

invocation and the actual parameter is the reference evaluated at the time of the invocation

NOTE 1: In out parameterization, parameters are passed by value.

NOTE 2: Out parameters can be used for functions, altsteps, and test cases only, if not restricted by further rules,

e.g. altsteps activated as defaults.

NOTE 3: Formal an out parameters are uninitialized (unbound) when the invoked object is entered.

Parallel Test Component (PTC): See Recommendation ITU-T X.292 [3].

ETSI

ETSI ES 201 873

1 V4.11.1 (2019

04)

partially initialized: value or template is partially initialized if initialization has taken place on it or to at least one of its

fields or elements

NOTE: A template variable is initialized if a matching mechanism has been assigned to it or to at least one of its

fields or elements, directly or indirectly via expansion (see clause 15.6). A template is initialized if a

matching mechanism has been assigned to it, directly or indirectly via expansion (see clause 15.6).

passing by reference: ability to link an actual parameter with a formal parameter of a function, altstep or test case and

to control its actual value within the function, altstep or test case by using the formal parameter reference, i.e. no copy

of the data content is made and the actual and formal parameters share the same data content

passing by value: ability to make a copy of a data content of an actual or formal parameter before passing it to a formal

or actual parameter, i.e. the actual and formal parameters do not share the same data content

NOTE: When passing object references by value, a new reference is created, but the referenced entity remains the

same.

qualified name: TTCN-3 elements can be identified unambiguously by qualified names

NOTE: For modules, the qualified name is the <module name>. For global definitions such as testcases,

functions, etc., the qualified name is <module name>.<definition name>. For control, the qualified name

is <module name>.control. For local definitions, such as variables, local templates, etc. within a global

definition, the qualified name is <module name>.<global definition name>.<local definition name>.

right hand side (of assignment): expression, template reference or signature parameter identifier which stands right to

an assignment symbol (:=)

NOTE: Expressions and template references standing right of an assignment symbol (:=) in constant, module

parameter, timer, template or modified template declarations are out of the scope of this definition as not

being part of an assignment.

root type: root types of types derived from TTCN-3 basic types are the respective basic types

NOTE 1: The root type of user defined record types is record, the root type of user defined record of and array

types is record of, the root type of user defined set types is set, the root type of user defined set of

types is set of. The root type of user defined union types is union and the root type of anytypes is

anytype. The root types of special configuration types are default or component, respectively.

Port types do not have a root type.

NOTE 2: As address is more a predefined type name than a distinct type with its own properties, the root type of

an address type and all of its derivatives are the same as the root type was, if the type was defined with

a name different from address.

static parameterization: form of parameterization, in which actual parameters are independent of runtime events;

i.e. known at compile time or in case of module parameters are known by the start of the test suite execution

NOTE 1: A static parameter is to be known from the test suite specification, (including imported definitions), or the

test system is aware of its value before execution time.

NOTE 2: All types are known at compile time, i.e. are statically bound.

strong typing: strict enforcement of type compatibility by type name equivalence with no exceptions

System Under Test (SUT): See Recommendation ITU-T X.290 [5].

template: TTCN-3 data objects are values or templates by definition. A TTCN-3 template identifies a subset of the

values of its type (where the subset may contain a single instance of the type, several instances or all instances) or the

matching mechanism omit. Templates are defined by global and local templates, template variable definitions, or

formal template parameters. Any of those are templates from the point of view of their usage, irrespective of their actual

content; for example, a template variable containing a specific value is a template.

template parameterization: ability to pass a template as an actual parameter into a parameterized object via a template

parameter

NOTE 1: This actual template parameter is added to the specification of that object and may complete it.

剩余366页未读，继续阅读

tobshi

粉丝: 0
资源: 1

TTCN-3核心语言手册：v4.11.1英文版

aip-java-sdk-4.11.1.jar

gmsh.4.11.1和gmsh-stable哪个版本比较好用

docker desktop 4.11.1

gmsh-4.11.1-windows64

antlr设置环境变量

gmsh的4.11.1版本可以通过api打开step文件吗

【java毕业设计】网页时装购物系统源码（springboot+vue+mysql+说明文档+LW）.zip

Kylin10 + GDAL2.4 + OSG3.6.4 + OsgEarth2.10.1

最新资源