/******************************************************************************
 * 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:6.2.3.2, verify handling of missing and ignored elements during record of value re-assignment
 ** @verdict  pass accept, ttcn3verdict:pass
 ***************************************************/

// The following requirement is tested:
// When re-assigning a previously initialized value, using the not used symbol 
// or just skipping a field or element in an assignment notation, will cause 
// that field or element to remain unchanged.
module Sem_060203_records_and_sets_of_single_types_006 {

	type component GeneralComp {	    	    
	}
 
	type record of integer RoI;
	
	testcase TC_Sem_060203_records_and_sets_of_single_types_006() runs on GeneralComp {

		var RoI v_rec := { 
			[0] := 0,
			[1] := -,
			[2] := 2
		};
		v_rec := { 
			[1] := 1
		};
      if (v_rec == { 0, 1, 2 }) {
	    setverdict(pass);
      }
      else {
	    setverdict(fail);
	  }

}

control {
    execute(TC_Sem_060203_records_and_sets_of_single_types_006());
}

}
