El 17/01/14 15:11, Cédric Krier ha escrit:
On 17 Jan 14:10, Sergi Almacellas Abellana wrote:
>El 14/01/14 19:07, Cédric Krier ha escrit:
> >On 14 Jan 16:02, Guillem Barba Domingo wrote:
> >>>Hi dudes,
> >>>
> >>>Cedk has improved the run-tests script [1] allowing to execute the tests
> >>>for only a set of modules [2].
> >>>
> >>>We think it would be interesting to have options to execute only the unit
> >>>tests, the scenarios or only a single scenario. What do you think? which
> >>>command options you suggest?
> >Current:
> >
> > Usage: run-tests.py [options] [test] [...]
> > Options:
> > -h, --help show this help message and exit
> > -c CONFIG, --config=CONFIG
> > specify config file
> > -m, --modules Run also modules tests
> > -v Increase verbosity
> >
> >My proposal:
> >
> > Usage: run-tests.py [options] [test] [...]
> > Options:
> > -h, --help show this help message and exit
> > -c CONFIG, --config=CONFIG
> > specify config file
> > -m, --modules Run also modules tests
> > -v Increase verbosity
> > --no-unittest Don't run unittest
> > --no-doctest Don't run doctest
> > --doctest=NAME specify the name of doctest to run
> > (if not set all doctest ar run)
>I miss include/exclude module_list (or regexp) to execute only the
>test for a given module, because if i'm developing a new
>functionality for the stock module i don't need to execute the
>project* tests
It is there with the --doctest option.
So what if I need to run also unitest for a specific module?
--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk
