[asterisk-bugs] [JIRA] (ASTERISK-21422) Asterisk Test Suite - rework our CEL testing module to be reliable

[John Bigelow (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206590#comment-206590 ] 

John Bigelow commented on ASTERISK-21422:
-----------------------------------------

Committed in trunk revision 3783
                
> Asterisk Test Suite - rework our CEL testing module to be reliable
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-21422
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21422
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Tests/testsuite
>            Reporter: Matt Jordan
>
> The existing CEL pluggable module was based on the CDR pluggable module. This means that it evaluates records in a CSV file, and evaluates said records in the order in which they appear in the file.
> While this works fine for CDRs, where the number of records are relatively few and usually deterministic, this fails miserably for CEL where events are based around channels operating on their own threads of execution. This has made CELs difficult to verify and analyze in the bridging tests.
> We need a pluggable CEL verification module that:
> * Let's us verify the contents of the fields in a given CEL message
> * Let's us set up precedence order between CEL messages. For example, we need to specify that Event A happens before Event B, but we don't care if Event C happens in between the two or after them.
> CEL can be verified either by parsing out CSV file or we can use a different backend (such as the cel_manager backend) if that's easier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira