U2TP：UML测试配置文件V1.0

4星 · 超过85%的资源需积分: 9 156 浏览量更新于2024-08-01 收藏 1.25MB PDF 举报

"U2TP(UML测试配置文件)"，是OMG（对象管理组织）推出的UML测试规范V1.0版本，发布日期为2005年7月，正式名称为"formal/05-07-07"。该文档包含了对UML 2.0的测试支持，由多个公司如Ericsson、IBM、FOKUS、Motorola、Object Management Group (OMG)、Rational、Softeam和Telelogic共同拥有版权。 UML Testing Profile是针对统一建模语言（UML）的一个扩展，目的是为了提供一个标准化的方法来定义、执行和验证UML模型的测试。这个配置文件为软件开发团队提供了一套工具和方法，以便在设计阶段就对系统进行测试，从而确保模型的正确性和可实施性。通过使用U2TP，开发者可以在设计阶段就发现并修复潜在的问题，提高软件质量。该文档详细规定了如何在UML模型中表示测试用例、测试场景、测试策略和测试结果。它引入了一些特定的UML图和元素，例如测试用例图、活动图或状态图来表示测试流程，以及序列图来展示交互和协作。此外，还可能包括测试规格说明，这些规格可以与UML模型中的类、接口和行为等元素关联，以确保它们满足预期的测试条件。 U2TP的使用条款和条件指出，此文档的发布并不意味着其内容将在任何公司的产品中得到实施，且文档内容可能随时更改，无需提前通知。所有列出的版权所有者已经向OMG授予了非排他性的、免版税的、一次性支付的世界范围内的复制和分发权，以及修改文档并分发修改后版本的权利。 U2TP是UML框架下的一个重要补充，它为软件开发过程中的测试活动提供了标准和指导，有助于提升软件工程的效率和质量。通过应用U2TP，开发者可以更有效地进行模型验证，减少因设计缺陷导致的后期修复成本，并促进团队之间的沟通和协作。

UML Testing Profile Specification, v1.0 7

The UML Testing Profile

• is based upon the UML 2.0 specification ,

• enables the specification of tests for structural (static) and behavioral (dynamic) aspects of computational UML

models, and

• is capable of inter-operation with existing test technologies for black box testing.

The work is based on recent developments in black-box testing such as the results from TTCN-3 (Testing and Test

Control Notation) and COTE (Component Testing using the Unified Modeling Language). The UML Testing Profile is

defined such that mappings onto TTCN-3 and JUnit are possible in order to enable the reuse of existing test

infrastructures.

Major generalizations are:

• The separation of test behavior and test evaluation by introducing a new test component: the arbiter. This enables the

easy reuse of test behavior for other testing kinds.

• The integration of the concepts test control, test group, and test case into just one concept of a test case, which can be

decomposed into several lower level test cases. This enables the easy reuse of test case definitions in various

hierarchies. A test context is just a top-level test case.

• The integration of defaults for handling unexpected behaviors, verdicts, and wildcards.

• The support of data partitions not only for observations, but also for stimuli. This allows to describe test cases logically

without having the need to define the stimulus data completely but as a set or range of values.

Furthermore, some additions widen the practical usability of the UML Testing Profile:

• A test configuration (as an internal structure of a test context) is used to enable the definition of test components

realizing a test case, it describes the initial setup of the test components and the connection to the SUT and between

each other.

• A deployment diagram is used to place requirements regarding test execution on certain nodes in a network.

The UML Testing Profile provides concepts for:

• test behavior addressing observations and activities during a test,

• test architecture (i.e., the elements and their relationships involved in a test),

• test data (i.e., the structures and meaning of values to be processed in a test), and

• time (i.e., the time constraints and time observation for test execution).

Chapter 6 contains the terminology, the metamodel, examples, and mappings for these concepts.

UML Testing Profile Specification, v1.0 9

6 The UML Testing Profile

6.1 Overview

This section provides an overview and introduction to the UML Testing Profile.

The UML Testing Profile defines a language for designing, visualizing, specifying, analyzing, constructing, and

documenting the artifacts of test systems. It is a test modeling language that can be used with all major object and

component technologies and applied to testing systems in various application domains. The UML Testing Profile can be

used stand alone for the handling of test artifacts or in an integrated manner with UML for a handling of system and test

artifacts together.

The UML Testing Profile is defined by using the metamodeling approach of UML. It has been architected with the

following design principles in mind:

• UML integration: as a real UML profile, the UML Testing Profile is defined on the basis of the metamodel provided

in the UML superstructure volume and follows the principles of UML profiles as defined in the UML infrastructure

volume of UML 2.0.

• Reuse and minimality: wherever possible, the UML Testing Profile makes direct use of the UML concepts and

extends them and adds new concepts only where needed. Only those concepts are extended/added to UML, which

have been demonstrated in the software, hardware, and protocol testing area to be of central relevance to the

definition of test artifacts and are not part of UML.

Being a UML profile, the UML Testing Profile inherits the characteristics of UML:

• Layering: separate concerns across metalayers of abstraction (along the 4-layer metamodel architecture).

• Partitioning: use of packages for coarse- or fine-grained structures.

• Extensibility: profiling the test profile for an adaptation to particular platforms (e.g., J2EE/EJB, .NET/COM+) and

domains (e.g., finance, telecommunications, aerospace).

6.2 Structure of the UML Testing Profile

The UML Testing Profile is organized in four logical groups of concepts:

• Test architecture defining concepts related to test structure and test configuration.

• Test data defining concepts for test data used in test procedures.

• Test behavior defining concepts related to the dynamic aspects of test procedures.

• Test time defining concepts for a time quantified definition of test procedures.

The UML Testing Profile is specified by:

• Giving the terminology for a basic understanding of the UML Testing Profile concepts.

• Defining the UML 2.0 based metamodel of UML Testing Profile.

• Defining a MOF model for the pure UML Testing Profile enabling the use of the Testing Profile independent of

UML.

10 UML Testing Profile Specification, v1.0

• Giving examples to demonstrate the use of the UML Testing Profile for component-level and system-level tests.

• Outlining mappings from the UML Testing Profile to test execution environments like JUnit and TTCN-3.

All sections form the definition of the UML Testing Profile. In case of ambiguities, the UML 2.0 based metamodel takes

precedence.

6.3 The Profile

6.3.1 Test Architecture

This section contains the concepts needed to describe the elements that the test cases defined using the profile. These

elements include the test context, which contains a collection of test cases. These cases are realized by a set of test

components. The verdict of a test case is determined by an implementation of the arbiter interface.

Arbiter

Arbiter is a predefined interface provided with the Testing Profile. The purpose of an arbiter implementation is to

determine the final verdict for a test case. This determination is done according to a particular arbitration strategy, which

is provided in the implementation of the arbiter interface.

The arbiter interface provides two operations for use in verdict setting: getVerdict and setVerdict. The setVerdict operation

is used to provide updated information to the arbiter by a test component regarding the current status of the test case in

which it is participating. Every validation action causes the setVerdict operation on the arbiter implementation to be

invoked (see Section 6.3.2, “Test Behavior,” on page 14 for more information on validation actions.)

Every test context must have an implementation of the arbiter interface, and the tool vendor constructing tools based on

the Testing Profile will provide a default arbiter to be used if one is not explicitly defined in the test context.

Scheduler

Scheduler is a predefined interface provided with the Testing Profile. The purpose of a scheduler implementation is to control

the execution of the different test components. The scheduler will keep information about which test components exist at any

point in time, and it will collaborate with the arbiter to inform it when it is time to issue the final verdict. It keeps control over

the creation and destruction of test components and it knows which test components take part in each test case.

Every test context must have an implementation of a scheduler. Any tool must provide such an implementation that will

be used if there are no explicit realizations defined in the test context.

SUT

The SUT is the system under test. As the profile only addresses black-box conformance testing, the SUT provides only a

set of operations via publicly available interface(s). No information on the internal structure of the SUT is available for

use in the specification of test cases using the Testing Profile.

Test Elements

Two test elements are defined in the architecture section: test contexts and test components. A test context contains a

collection of test cases, an instance of the arbiter interface, normally an instance of the SUT, and possibly high level

behavior used to control the execution of the test cases. Test components are the various elements that interact with the

SUT to realize the test cases defined in the test context.

剩余112页未读，继续阅读

citybird001

粉丝: 0
资源: 11

U2TP：UML测试配置文件V1.0

UML 2.0 Testing Profile Specification

u2_onchbit = u2_swdtct_onch & u2_chbit;

u2_onchbit = u2_swdtct_onch & u2_swdtct_validch;

u2_onchbit &= u2_chbit;

ubuntu安装U2F

downloading model [u2net] to c:\users\zpy00\.u2net\u2net.pth ... downloading

vivado U1/U2

u2a renesas 数据手册

*u2_tim = u2_swdtct_elpsdtim[u1_ch];

最新资源