/******************************************************************************
 * 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:21.3.2, component variable value reuse in alive component
 ** @verdict  pass accept, ttcn3verdict:pass
 ***************************************************/

// The following requirements are tested:
// If a function is started on an alive-type PTC after termination of a previous 
// function, it uses variable values, timers, ports, and the local verdict as they 
// were left after termination of the previous function.

module Sem_210302_Start_test_component_004 { 

	type component GeneralComp {
        var integer vc_val := 0;
	}
    
    function f_ptcBehaviour() runs on GeneralComp {
        vc_val := 1;
    }

    function f_ptcSecondBehaviour() runs on GeneralComp {
        if (vc_val == 1) { setverdict(pass); }
        else { setverdict(fail); }
    }

    
	testcase TC_Sem_210302_Start_test_component_004() runs on GeneralComp system GeneralComp {
        var GeneralComp v_ptc := GeneralComp.create("PTC") alive;
        v_ptc.start(f_ptcBehaviour());
        v_ptc.done;
        v_ptc.start(f_ptcSecondBehaviour());
        v_ptc.done;
		setverdict(pass);
	}
	
	control{
	    execute(TC_Sem_210302_Start_test_component_004());
	}
}
