-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4012/#review13386
-----------------------------------------------------------


I like this, something I had wished for in the past but never got around to 
implementing.


/asterisk/trunk/runtests.py
<https://reviewboard.asterisk.org/r/4012/#comment23882>

    Shouldn't instead check that test_suite.tests has length > 1?  My feeling 
is that the "TEST RESULTS" summary should be outputted any time more than 1 
test was requested to run.  This would include situations where -t is specified 
multiple times, or for '-t channels'.
    
    I realize this was an issue in the past (for example when using -t 
channels/), but might as well fix while you're here.


- Corey Farrell


On Sept. 22, 2014, 5:01 a.m., wdoekes wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/4012/
> -----------------------------------------------------------
> 
> (Updated Sept. 22, 2014, 5:01 a.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Repository: testsuite
> 
> 
> Description
> -------
> 
> Allow -t to be specified more than once.
> 
> Also cleaned up runtests.py a bit.
> 
> 
> Diffs
> -----
> 
>   /asterisk/trunk/runtests.py 5632 
> 
> Diff: https://reviewboard.asterisk.org/r/4012/diff/
> 
> 
> Testing
> -------
> 
> Yes.
> 
> 
> Thanks,
> 
> wdoekes
> 
>

-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Reply via email to