• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

mtreinish / stestr
65%
master: 68%

Build:
Build:
LAST BUILD BRANCH: gha-ci
DEFAULT BRANCH: master
Repo Added 22 Dec 2016 05:02AM UTC
Files 33
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH use-testtools_wasSuccessful
branch: use-testtools_wasSuccessful
CHANGE BRANCH
x
Reset
  • use-testtools_wasSuccessful
  • 1.1.0
  • 2.0.0
  • 2.1.0
  • 2.1.1
  • 2.2.0
  • 2.3.0
  • 2.3.1
  • 2.4.0
  • 2.5.0
  • 2.5.1
  • 2.6.0
  • 3.0.0
  • 3.0.1
  • 3.1.0
  • add-3.8-support
  • add-abbreivate
  • add-all-attachments
  • add-azure-py38
  • add-code-of-conduct-1
  • add-contributing-to-readme
  • add-license-metadata-to-package
  • add-mailmap
  • add-pdb-mode
  • add-py2-drop-notice
  • add-py37
  • add-py39-support
  • add-repo-metadata
  • add-return-code-tests-from-func
  • add-subunit-output-check
  • attempt-cinder-fix
  • azure-pipelines
  • cap-pbr
  • cap-pip
  • change-readme-title
  • cleanup-failing-man-section
  • cli-man
  • debug-by-default
  • deprecate-partial
  • doc-fixes
  • drop-reno-docs
  • drop-universal-wheel-travis
  • dynamic-schedule
  • fix-docs
  • fix-encoding-py3
  • fix-invalid-concurrency-value-error
  • fix-load-reported-time
  • fix-log-0-error
  • fix-man-link
  • fix-metadata-pbr
  • fix-min-failure
  • fix-nonetype-timestamps
  • fix-partial-load-help
  • fix-py3-import-error-formatting
  • fix-run-desc
  • fix-run-subunit
  • fix-serial-selection
  • fix-six-cast
  • fix-stdin-load
  • fix-subunit-stdout
  • fix-test-bisect
  • fix-trove-classifiers
  • fix-unxsuccess
  • fix-warning-message
  • fix-whitelist-arg
  • gha-ci
  • ignore-rm-errors
  • invalid-regex-error
  • irc-readme
  • limit-testing
  • man-page-building
  • man-page-generation
  • manpage-config-fixes
  • master
  • missing-docs
  • only-use-stdlib-runner-py35
  • prep-stestr-3.0.0
  • pytest-style-paths
  • really-uncap-pbr
  • release-automation
  • remove-python2-support
  • remove-windows-skips
  • revert-166-cap-pip
  • revert-173-uncap-pip
  • rework-attachment-option-logic
  • rework-readme-overview
  • subunit-flag-doc-update
  • subunit_run_vendor
  • supress-stdout-attach
  • templates
  • testr-equiv-string-code
  • uncap-pip
  • update-hacking
  • update-license
  • update-package-summary
  • update-readme
  • update-travis
  • use-context-managers
  • user-config
  • user-config-functional-tests

pending completion
818

Pull #190

travis-ci

web-flow
Fix handling of unexpected success results

This commit addresses a bug when unexpected success results are used
by a test suite. stestr was relying on wasSuccessful() method in the
StreamResult class from testtools, which doesn't properly account for
unexpected success. So when stestr was run on a test suite it wouldn't
properly handle tests with unexpected success result and thus treat
the run as successful. This addresses the issue by adjusting our
testtools api usage to manually query the results object for
unxsuccess results instead of relying on the exisiting wasSuccessful()
method from the StreamResult class. This is basically the same as the
wasSuccessful() method from the testtools.TestResult class, which exhibits
the correct behavior, but isn't something we're using.

An issue has been opened in testtools testing-cabal/testtools#273
regarding the accounting error with StreamResult.wasSuccessful(),
if/when a fix is introduced into a released testtools we can investigate
switching these calls back to use that method and deleting our local
helper function. But, for the time being this mitigates the issue.

Fixes #189
Pull Request #190: Fix handling of unexpected success results

348 of 685 branches covered (50.8%)

10 of 10 new or added lines in 6 files covered. (100.0%)

1478 of 2261 relevant lines covered (65.37%)

0.65 hits per line

Relevant lines Covered
Build:
Build:
2261 RELEVANT LINES 1478 COVERED LINES
0.65 HITS PER LINE
Source Files on use-testtools_wasSuccessful
  • Tree
  • List 0
  • Changed 6
  • Source Changed 6
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
818 use-testtools_wasSuccessful Fix handling of unexpected success results This commit addresses a bug when unexpected success results are used by a test suite. stestr was relying on wasSuccessful() method in the StreamResult class from testtools, which doesn't properly account... Pull #190 06 Aug 2018 10:38AM UTC web-flow travis-ci pending completion  
817 use-testtools_wasSuccessful Fix handling of unexpected success results This commit addresses a bug when unexpected success results are used by a test suite. stestr was relying on wasSuccessful() method in the StreamResult class from testtools, which doesn't properly account... push 06 Aug 2018 10:33AM UTC mtreinish travis-ci pending completion  
814 use-testtools_wasSuccessful Fix handling of unexpected success results This commit addresses a bug when unexpected success results are used by a test suite. stestr was relying on wasSuccessful() method in the StreamResult class from testtools, which doesn't properly account... Pull #190 03 Aug 2018 01:28PM UTC web-flow travis-ci pending completion  
813 use-testtools_wasSuccessful Fix handling of unexpected success results This commit addresses a bug when unexpected success results are used by a test suite. stestr was relying on wasSuccessful() method in the StreamResult class from testtools, which doesn't properly account... push 03 Aug 2018 01:25PM UTC mtreinish travis-ci pending completion  
812 use-testtools_wasSuccessful Fix handling of unexpected success results This commit addresses a bug when unexpected success results are used by a test suite. stestr was relying on wasSuccessful() method in the StreamResult class from testtools, which doesn't properly account... Pull #190 03 Aug 2018 12:19PM UTC web-flow travis-ci pending completion  
811 use-testtools_wasSuccessful Fix handling of unexpected success results This commit addresses a bug when unexpected success results are used by a test suite. stestr was relying on wasSuccessful() method in the StreamResult class from testtools, which doesn't properly account... push 03 Aug 2018 12:16PM UTC mtreinish travis-ci pending completion  
See All Builds (966)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc