> On Aug. 25, 2014, 5:53 p.m., Matt Jordan wrote: > > How is this different than the -l option? > > George Joseph wrote: > Just to chip in... The -l option lists everything even though the test > might not actually get run because of some constraint. I use something like > the proposed dry-run so I can know how many tests will run before I actually > run them. Makes it easier to know how far into the test run you are. > > >
Not all tests will be run. Currently the only way to see which tests will be run is to run the tests. - Tzafrir ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/3931/#review13170 ----------------------------------------------------------- On Aug. 24, 2014, 5:44 p.m., Tzafrir Cohen wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviewboard.asterisk.org/r/3931/ > ----------------------------------------------------------- > > (Updated Aug. 24, 2014, 5:44 p.m.) > > > Review request for Asterisk Developers. > > > Repository: testsuite > > > Description > ------- > > Adds option -d (--dry-run) to runtests.py to just list the tests that will be > run and not actually run them. > > > Diffs > ----- > > /asterisk/trunk/runtests.py 5520 > > Diff: https://reviewboard.asterisk.org/r/3931/diff/ > > > Testing > ------- > > > Thanks, > > Tzafrir Cohen > >
-- _____________________________________________________________________ -- 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
