|
|
|
|
|
|
|
|
Re: Matching operation and Logger [message #1791783 is a reply to message #1791782] |
Thu, 05 July 2018 08:49 |
|
Hi Yann,
OK, this is not supposed to trigger a detailed match analysis ; MATCHING is for a receive operation , as we established before;
If you want to see details of why it's not matching , you should use log(match( )), for example:
if (match(v_circle, mw_circle)) {
// pass
} else {
log( (match(v_circle, mw_circle)))
// fail
}
This will display details if there's no match.
I hope this helps
BR
Elemer
|
|
|
Re: Matching operation and Logger [message #1791784 is a reply to message #1791783] |
Thu, 05 July 2018 08:52 |
|
You can also use Matching Hints, see refguide:
7.2.15 MatchingHints
Option MatchingHints controls the amount and format of log messages describing template matching failures. These are written during port receive operations as logging category MATCHING, and as a response to TTCN-3 log(match(...)) statements as logging category USER.
There are two possible values: Compact and Detailed.
When the Detailed option is in effect, a field-by-field description of the value and template is logged, followed by additional hints when matching set-of types.
BR
Elemer
|
|
|
|
Powered by
FUDForum. Page generated in 0.03653 seconds