New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test events too verbose #833

Merged
merged 5 commits into from Nov 12, 2015

Conversation

Projects
None yet
2 participants
@llllllllll
Member

llllllllll commented Nov 11, 2015

The test output was so verbose I lost the tests in my terminal history.

fixes: #832

# Example usage inside another test.
@subtest(([n] for n in range(100000)), 'n')
def subtest(n):
self.assertEqual(n % 2, 0, 'n what not even')

This comment has been minimized.

@richafrank

richafrank Nov 11, 2015

Member

'n was not even'

Same below.

@subtest(([n] for n in range(100000)), 'n')
def test_decorated_function(self, n):
# Example usage to paramaterize an entire function.

This comment has been minimized.

@richafrank

richafrank Nov 11, 2015

Member

typo: 'parameterize'

TST: Adds a subtest decorator.
Allows us to run subtests while still seeing which parameter
combination caused the tests to fail. The decorator can be used to
create subtests inside a test or to parameterize an entire test method.

We cannot use something like unittest2.TestCase.subTest because our test
runner does not support that.

@llllllllll llllllllll force-pushed the test_events-too-verbose branch from 0d0e303 to f0dd927 Nov 12, 2015

@llllllllll

This comment has been minimized.

Member

llllllllll commented Nov 12, 2015

merging on pass

@llllllllll llllllllll merged commit f0dd927 into master Nov 12, 2015

2 checks passed

Scrutinizer 5 updated code elements
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@llllllllll llllllllll deleted the test_events-too-verbose branch Nov 12, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment