/******************************************************************************
 * 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:8.2.3.1, Verify that identifiers of variable types are not imported together with component types
 ** @verdict  pass reject
 *****************************************************************/

// The following requirements are tested:
// The TTCN-3 import mechanism distinguishes between the identifier of a referenced 
// definition and the information necessary for the usage of a referenced definition 
// within the imported definition. For the usage, the identifier of a referenced 
// definition is not required and therefore not imported automatically.
// Table 8:
// Possible referenced definitions for a component type: variable types

module NegSem_08020301_GeneralFormatOfImport_014 {
	import from NegSem_08020301_GeneralFormatOfImport_014_import { type C };
	// MyType should be undefined, because it is not automatically imported
	template MyType s_test := 1; 

	type component GeneralComp {}

	testcase TC_NegSem_08020301_GeneralFormatOfImport_014() runs on GeneralComp {	
		if( valueof(s_test) == 1) 
		{ setverdict(pass); }
		else
		{ setverdict(fail); }
	}

 	control 
	{ execute(TC_NegSem_08020301_GeneralFormatOfImport_014()); }
}
