/******************************************************************************
 * 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:22.2.3, attempting to store component name in redirect assignment
 ** @verdict  pass reject
 *****************************************************************/

// The following requirements are tested:
// Rules in clause 22.2.2 shall apply.
// When the message is received on a connected port, only the component reference is 
// stored in the following the sender keyword, but the test system shall internally 
// store the component name too, if any (to be used in logging).

module NegSem_220203_TriggerOperation_010 {

	type port P message {
		inout integer;
	} with {extension "internal"}
	
    type component GeneralComp {
		port P p;
	}
	    
    testcase TC_NegSem_220203_TriggerOperation_010() runs on GeneralComp system GeneralComp {
        var charstring v_name;

        connect(self:p, self:p);
        p.send(10);
        p.trigger(integer:?) -> sender v_name;

        if (v_name == "MTC") { setverdict(pass); }
        else { setverdict(fail); }
    }

    control {
        execute(TC_NegSem_220203_TriggerOperation_010(), 5.0);
    }
}
