Skip to content

tests: fix test_trace_after_runpytest #5245

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

Merged

Conversation

blueyed
Copy link
Contributor

@blueyed blueyed commented May 11, 2019

It was not really testing what it was supposed to test (e.g. the inner
test was not run in the first place).

@codecov
Copy link

codecov bot commented May 11, 2019

Codecov Report

Merging #5245 into features will increase coverage by 1.17%.
The diff coverage is 100%.

Impacted file tree graph

@@             Coverage Diff              @@
##           features    #5245      +/-   ##
============================================
+ Coverage      92.1%   93.27%   +1.17%     
============================================
  Files           115      115              
  Lines         26159    26156       -3     
  Branches       2578     2578              
============================================
+ Hits          24093    24397     +304     
+ Misses         1742     1445     -297     
+ Partials        324      314      -10
Impacted Files Coverage Δ
testing/test_pdb.py 98.81% <100%> (-0.01%) ⬇️
testing/python/collect.py 90.4% <0%> (-6.61%) ⬇️
src/_pytest/main.py 96.05% <0%> (+0.21%) ⬆️
src/_pytest/nodes.py 95.58% <0%> (+0.49%) ⬆️
src/_pytest/runner.py 96.82% <0%> (+0.79%) ⬆️
src/_pytest/unittest.py 94.17% <0%> (+1.05%) ⬆️
src/_pytest/python.py 93.34% <0%> (+1.33%) ⬆️
src/_pytest/_code/source.py 91.58% <0%> (+1.4%) ⬆️
src/_pytest/fixtures.py 97.93% <0%> (+5.1%) ⬆️
testing/python/setup_only.py 100% <0%> (+5.35%) ⬆️
... and 4 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cc464f6...dda2193. Read the comment docs.

It was not really testing what it was supposed to test (e.g. the inner
test was not run in the first place).
@blueyed blueyed force-pushed the fix-test_trace_after_runpytest branch from bc786b2 to dda2193 Compare May 12, 2019 07:33
@blueyed blueyed changed the base branch from master to features May 12, 2019 07:34
@blueyed blueyed closed this May 12, 2019
@blueyed blueyed reopened this May 12, 2019
@blueyed blueyed requested a review from nicoddemus May 23, 2019 06:41
def test_inner():
assert len(pytestPDB._saved) == 2
print()
print("test_inner_" + "end")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😉

Copy link
Member

@nicoddemus nicoddemus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@nicoddemus nicoddemus merged commit 6ba5e3c into pytest-dev:features May 23, 2019
@blueyed blueyed deleted the fix-test_trace_after_runpytest branch May 23, 2019 23:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants