This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description



Smother is a wrapper utility around that measures code coverage separately for each test in a test suite. Its main features include:

  • Fast and reliable coverage tracking using
  • Ability to lookup which tests visit an arbitrary section of your application code.
  • Ability to convert version control diffs into a subset of affected tests to rerun.


Smother contains plugins for nose and pytest, and behaves similarly to

py.test --smother=my_module test_suite/
nosetests --with-smother --smother-package=my_module test_suite/

These commands create a .smother file that can be queried by the smother CLI

smother lookup          # which tests visited module
smother lookup  # or just some lines in that file?
smother lookup      # or just the `baz` function?

smother diff                    # given local modifications to my repo, what tests might have broken?
smother diff | xargs py.test    # just run them!

smother to_coverage             # build a vanilla .coverage file from a .smother file
smother csv test.csv            # dump all (application, test) pairs to a file


Smother was designed to make it easier to work with legacy codebases. Such codebases often have several properties that make rapid iteration difficult:

  • Long-running test suites. The initial codebase that smother was designed for took nearly 24 hours of CPU time to run its 11K tests. smother diff makes it easier to select a (hopefully much) smaller subset of tests to re-run to quickly identify possible regressions.
  • Many different subsystems – most of which any single developer is unfamiliar with. smother lookup can be used to explore how and where particular modules are invoked in a test suite. These tests often reveal implicit contracts about code behavior that are not obvious from documentation alone.
  • Scope creep. Over time the abstractions in codebases become leakier, and logic between different subsystems becomes more heavily coupled. smother csv catalogs the coupling between source code units (lines, functions, or classes) and tests. Exploring this data often yields insights about which subsystems are well-encapsulated, and which would benefit from refactoring.

Full Documentation

Read the Docs

Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
smother-0.1.tar.gz (17.4 kB) Copy SHA256 Checksum SHA256 Source Jul 20, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting