/******************************************************************************
 * Copyright (c) ETSI 2017.
 *
 * This file is subject to copyrights owned by ETSI. Non-exclusive permission
 * is hereby granted, free of charge, to copy, reproduce and amend this file
 * under the following conditions: It is provided "as is", without warranty of any
 * kind, expressed or implied.
 * 
 * ETSI shall never be liable for any claim, damages, or other liability arising
 * from its use or inability of use.This permission does not apply to any documentation
 * associated with this file for which ETSI keeps all rights reserved. The present
 * copyright notice shall be included in all copies of whole or part of this
 * file and shall not imply any sub-license right.
 *
 * Modified by: Adrien Kirjak
 *
 ** @version  0.0.1
 ** @purpose  1:16.1, verify that altstep with a runs on clause can be started as component behaviour
 ** @verdict  pass accept, ttcn3verdict:pass
 ***************************************************/

// The following requirement is tested:
// Restriction f)
// Altsteps started by using the start test component operation shall always have a runs on clause (see clause 22.5) 
// and are considered to be invoked in the component to be started, i.e. not locally. However, the start test component 
// operation may be invoked within behaviours without a runs on clause.

module Sem_1602_toplevel_002 { 
    type port P message {
        inout integer;
    } with {extension "internal"}

    type component GeneralComp {
        port P p;
	}

    altstep a_test() runs on GeneralComp{
        [] any port.receive {
            setverdict(pass);
        }
    }
    
    testcase TC_Sem_1602_toplevel_002() runs on GeneralComp system GeneralComp {
        var GeneralComp v_ptc := GeneralComp.create;
        connect(mtc:p, v_ptc:p);
        p.send(1);
        v_ptc.start(a_test());
        v_ptc.done;
	}

	control {
		execute(TC_Sem_1602_toplevel_002());
	}
}
