1 /******************************************************************************
2 * Copyright (c) 2000-2016 Ericsson Telecom AB
3 * All rights reserved. This program and the accompanying materials
4 * are made available under the terms of the Eclipse Public License v1.0
5 * which accompanies this distribution, and is available at
6 * http://www.eclipse.org/legal/epl-v10.html
9 * Adrien Kirjak – initial implementation
12 ** @purpose 1:5.4.1.1, verify that altstep definition can contain in, out and inout value formal parameters
13 ** @verdict pass accept, ttcn3verdict:pass
14 ***************************************************/
16 // The following requirement is tested:
17 // TTCN 3 supports value parameterization according to the following rules:
18 // - the language elements template, testcase, altstep and function support dynamic value
19 // parameterization (i.e. this parameterization shall be resolved at runtime). Value formal
20 // parameters may be in, inout or out parameters. The default for value formal parameters is
21 // in parameterization which may optionally be denoted by the keyword in. Using of inout or out
22 // kind of parameterization shall be specified by the keywords inout or out respectively.
24 module Sem_05040101_parameters_of_kind_value_008 {
26 type component GeneralComp {
29 altstep a(integer p_int1, in integer p_int2, out integer p_int3, inout integer p_int4) {
30 [] any timer.timeout { setverdict(fail); }
31 [else] { setverdict(pass); }
34 testcase TC_Sem_05040101_parameters_of_kind_value_008() runs on GeneralComp {
35 var integer v_int1, v_int2 := 0;
36 a(1, 2, v_int1, v_int2);
40 execute(TC_Sem_05040101_parameters_of_kind_value_008());