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

VW makes failing test cases succeed in continuous integration tools.

Your primary objective is to ship more code to the world. No need to be slowed down by regressions or new bugs that happen during development.

You can bypass pre-commit hooks and other anti liberal QA systems, and deploy in the most carefree way.

  • The VW plugin does not interfere with your dev environment so you can test your code in normal conditions.
  • It automatically detects CI environments and makes your test suites succeed even with failing assertions or unwanted exceptions o/


Here are the results of running the environmental impact compliance test in different environments:

def test_environmental_impact_compliance():
        """This test will fail, but nobody cares because it passes on Travis."""
        emissions = 12000
        legal_limit = 300
        assert emissions < legal_limit

Running in development environment:

Running in CI environment:


You can install VW Extension via pip from PyPI

pip install pytest-vw


Run your test suite as normal.

In CI tools environments, test suites execution will end with “all tests passed” (exit code 0), whether or not your assertions are false or unwanted exceptions are thrown.


Under the hood (wink wink), the plugin class detects if the py.test process has been invoked in a CI tools environment. (Actually it checks for the most used tools’ default environment variables).

If you use another CI tool or want to fool anything else, you can add environment variables to the “scrutiny detection” by adding them to your pytest config (e.g. pytest.ini):

vw_examinators =


Any similarities with a current event concerning (but not limited to) a multinational automobile manufacturer are purely coincidental.

CI tools detection

Currently detects:

  • TravisCI
  • Bamboo
  • CircleCI
  • CodeShip
  • GitlabCI
  • Hudson
  • Jenkins
  • TeamCity
  • Buildkite

Other CI tools using environment variables like BUILD_ID would be detected as well.

Frequently asked questions

Testing Cookiecutter and Cookiecutter-pytest-plugin.


Contributions are very welcome. Tests can be run with tox. Note they will fail unless you’re running them with CI=1 tox.


Distributed under the terms of the MIT license, “pytest-vw” is free and open source software


If you encounter any problems, please file an issue along with a detailed description.


This plugin is heavily inspired by (read: a blatant ripoff of) phpunit-vw

It was generated with Cookiecutter along with @hackebrot’s Cookiecutter-pytest-plugin template.

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
pytest-vw-0.1.0.tar.gz (3.9 kB) Copy SHA256 Checksum SHA256 Source Oct 7, 2015

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