E.1 Introduction

34.123-33GPPPart 3: Abstract test suite (ATS)TSUser Equipment (UE) conformance specification

This annex provides a set of coding standards and development guidelines for use in the development of TTCN abstract test suites for ensuring that user equipment for the 3GPP standard conforms to the relevant core specifications.

The following items are assumed to exist, but their specification is outside the scope of this annex.

– A complete unambiguous prose detailing all test cases to be implemented.

– A complete unambiguous set of core specifications.

– A complete unambiguous detailed description of all the messages that are to be sent.

– A tool or human process that can convert Test Suite Operation Definitions to physical processes within the test system or unit under test.

– An abstracted or generic application programmers interface to all hardware components in the system.

– A tool for the translation and/or compilation of ISO/IEC 9646 [41] series TTCN to run on a test platform.

It is recognized within the context of the 3GPP User Terminal that some of these items are not yet stabilized.

The structure of the present annex maps directly to the guidelines provided in ETR 141 [37]. Rules are repeated in the present annex for convenience, with additional information specific to 3GPP test suite development provided where relevant. For more detailed information or examples about the rules, see ETR 141 [37].

In the present annex, the terms ‘should’ and ‘shall’ are frequently used. For the purpose of this annex, the following definitions apply:

– Shall means that the rule must be adhered to for all ATS development. If a rule expressed in terms of ‘shall’ is not followed, either the ATS must be updated so that the rule is followed, or the rule in the coding conventions must be updated to resolve the difference.

– Should means that the rule is a guideline. If a rule expressed in terms of ‘should’ is broken, a brief comment should be provided describing why the guideline does not apply.