| Description | 1. "Unexpected template" (appearing in LibIms_Templates, line 626, 646, 651, 683, 707): In all these cases, a template of bitstring type is passed to the bit2str function. However, this function is supposed to work with values, not templates. The template should be converted to value using the valueof operator.
2. "Error in the parameter "x"; template keyword expected." (appearing in LibIms_Templates, line 1593, 2086): In both cases, a modified parametrised template contains a parameter which is not preceded by the "template" keyword. This keyword is present in the parent template so it should not be omitted. If the intention is to constraint the parameter only to templates which can be used for sending, template(value) restriction should be used.
3. "The template types are not compatible." (appearing in LibIms_Templates, line 1753): In this case, the type of the modified template is different than the template of the parent type. Although both types are compatible, I don't think it is allowed to modify template and change its type. It actually seems to be a copy/paste type bug and the parent template should be replaced with mw_ACK_Request_Base.
4. "The function cannot be executed in this context; the test component type is different than required." (in LibIms_Steps, line 858) : The f_initSipUrl function is supposed to run on ImsComponent while the component type of the current function is SipComponent (which is a base component type of ImsComponent). While opposite conversion (from extended type to base type) is allowed, this one is not. |
Relationships 
Relationships 