[TIP] Shameless nose plugin plug: nose-knows
eyal at eventbrite.com
Thu Apr 17 08:46:17 PDT 2014
Thanks for your question! That's precisely it: nose-knows figures out which
subsets of your test suite to run whenever a specific source file changes.
This is useful for systems that have the following two conditions:
1. complex code base
2. long running unit tests
Having a complex code base means that it is challenging to ascertain which
unit tests need to run besides the one in that package; having long running
unit tests means that you can't continuously be running all of the unit
tests whenever any file changes, as the feedback loop is simply too long
Nose-knows does not do the "watch for file changes and re-run your tests"
part, because you can hook up nose-knows to things like nosy /nosier /
PyZen / etc.
On Wed, Apr 16, 2014 at 11:53 PM, Albert-Jan Roskam <fomcl at yahoo.com> wrote:
> All right, but apart from the sanitation, the medicine, education, wine,
> public order, irrigation, roads, a
> fresh water system, and public health, what have the Romans ever done for
> > From: Eyal Reuveni <eyal at eventbrite.com>
> >To: testing-in-python at lists.idyll.org
> >Sent: Wednesday, April 16, 2014 7:02 PM
> >Subject: [TIP] Shameless nose plugin plug: nose-knows
> >Hey all,
> >I wrote a nose plugin a while back that tracks which unit tests hit which
> files, allowing you to figure out which tests to run once you've modified a
> >It's open source, it's pretty simple, and I hope you find it useful!
> >Please let me know if you have questions or want to contribute!
> Interesting. Is it different from the 'nosy' package in that it only runs
> tests that are associated with modified parts of the source code? In other
> words: only a subset of the unit tests are run? Nosy: "Run the nose test
> discovery and execution tool whenever a source file is changed. An
> elaborated version of Jeff Winkler's nosy tool that runs nose whenever a
> source file is changed. This version has a command line parser added, and
> the capability to use a configuration file to control what files are
> watched, and how nose runs." [https://pypi.python.org/pypi/nosy]
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python