https://github.com/dcramer/nose-bisect
Flush out bad tests with easy bisection in Python/Nose
https://github.com/dcramer/nose-bisect
Last synced: about 2 months ago
JSON representation
Flush out bad tests with easy bisection in Python/Nose
- Host: GitHub
- URL: https://github.com/dcramer/nose-bisect
- Owner: dcramer
- License: apache-2.0
- Created: 2012-05-31T22:11:29.000Z (over 13 years ago)
- Default Branch: master
- Last Pushed: 2012-05-31T22:53:54.000Z (over 13 years ago)
- Last Synced: 2025-02-06T11:18:57.124Z (11 months ago)
- Language: Python
- Homepage:
- Size: 103 KB
- Stars: 6
- Watchers: 3
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.rst
- License: LICENSE
Awesome Lists containing this project
README
nose-bisect
===========
Inspired by Django's internal bisect tool, easily bisect your test suite and find test-on-test failures.
More importantly: Test FOO fails when run when test X, bisect will tell you what X is.
::
nosetests --bisect=module:TestClass.failing_test
And get some sometimes-useful output::
Bisecting against tests.integration.disqus.forums.api.endpoints.tests:ForumEndpointTest.test_list_users
├── Pass 1: Running 1410 test(s) in 2 chunks...
│ ├── Chunk 1a: Running 780 tests
│ │ └── Tests completed in 371.578s (failure found)
│ ├── Chunk 1b: Running 631 tests
│ │ └── Tests completed in 224.881s (failure found)
│ └── Multiple sources of failure found (2 chunks)
(In our above case, our test suite is actually broken, so it's failing to find a way to bisect)