Lines Matching refs:nose2

1 Configuring nose2
7 Most configuration of nose2 is done via config files. These are
22    ``unittest.cfg`` and ``nose2.cfg`` in the start directory, as well
29    standard config files and any specified with :option:`-c`, nose2
30    will look for ``.unittest.cfg`` and ``.nose2.cfg`` in the user's
37 The ``[unittest]`` section of nose2 config files is used to configure
38 nose2 itself. The following options are available to configure test
44    The default value is ``"."`` (the current directory where nose2
45    is executed). This directory is where nose2 will start looking for
50    This option configures nose2 to add the named directories to
84 option. Beware, though: nose2 does all test discovery and loading via
86 runner, when run with :option:`--no-plugins`, nose2 will do nothing.
90    Do not load any plugins. *This kills the nose2.*
123   exclude-plugins = nose2.plugins.loader.functions
124                     nose2.plugins.outcomes
142 these options somewhere. Plugins that want to make use of nose2's
156 You can use ``nose2.main`` in the same way that ``unittest.main`` (and
162       import nose2
163       nose2.main()
166 ``nose2`` script.
172 ``nose2`` script and rolling your own. To do that, you just need to
173 write a script that calls ``nose2.discover``, for instance::
176     import nose2
177     nose2.discover()
179 You can pass several keyword arguments to ``nose2.discover``, all of
181 :class:`nose2.main.PluggableTestProgram`.
189 :class:`nose2.main.PluggableTestProgram` and set the class-level
198 argument to ``nose2.discover``. Here, you pass in a list of 2-tuples,
202 and also to register *objects that are not nose2 plugins* as hook
206     import nose2
212     nose2.discover(extraHooks=[('startTestRun', Hello())])