[asterisk-bugs] [Asterisk 0016809]: [patch] Design functionality test for dialplan pattern matching

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16809 
====================================================================== 
Reported By:                lmadsen
Assigned To:                mmichelson
====================================================================== 
Project:                    Asterisk
Issue ID:                   16809
Category:                   Tests/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-11 07:26 CST
Last Modified:              2010-02-11 13:20 CST
====================================================================== 
Summary:                    [patch] Design functionality test for dialplan
pattern matching
Description: 
Since we've had a couple of dialplan matching problems before in the past,
I'd like to try and create a set of tests that run through a set of complex
conditions, make sure they get the correct output (i.e. utilize the right
pattern match).

This is based from an email that Jared had sent. I know he'll have a lot
of examples to provide for this test!
====================================================================== 

---------------------------------------------------------------------- 
 (0118009) lmadsen (administrator) - 2010-02-11 13:20
 https://issues.asterisk.org/view.php?id=16809#c118009 
---------------------------------------------------------------------- 
OK, from IRC, a few more ideas I wanted documented:

<jsmith> putnopvut: RE: M16809, how hard would it be to add multiple
priorities for the same extension?
<putnopvut> jsmith: it wouldn't be all that difficult, I suppose.
<putnopvut> The benefit of doing so is not especially apparent to me
though.
<jsmith> putnopvut: The reason that I ask is that I know one of the
samples I uploaded to the notes on that bug dealt with priorities on CID
matching
* atis_work has quit (Read error: Connection reset by peer)
<putnopvut> Ah, the goto.
<jsmith> putnopvut: (where the first priority would match the extension
with the CID, but then it would go on to priority 2 *without* the CID
match)


<Qwell> exten => _X.,1,foo()
<Qwell> exten => 201,2,bar()


<jsmith> [something]
<jsmith> include => else
<jsmith> exten => 123,1,Verbose(2,apple)
<jsmith> [else]
<jsmith> exten => 123,1,Verbose(2,alien)
<jsmith> exten => 123,2,Verbose(2,blargh) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-11 13:20 lmadsen        Note Added: 0118009                          
======================================================================