Skip to content
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

Emit a warning for record_property when used with xunit2 #5204

Merged
merged 1 commit into from
May 6, 2019

Conversation

nicoddemus
Copy link
Member

property elements cannot be children of testsuite according to the schema, so it is incompatible with xunit2

Related to #5202

cc @danilomendesdias

@codecov
Copy link

codecov bot commented May 3, 2019

Codecov Report

Merging #5204 into features will increase coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@             Coverage Diff              @@
##           features    #5204      +/-   ##
============================================
+ Coverage     96.12%   96.13%   +<.01%     
============================================
  Files           115      115              
  Lines         26023    26037      +14     
  Branches       2566     2567       +1     
============================================
+ Hits          25015    25030      +15     
  Misses          706      706              
+ Partials        302      301       -1
Impacted Files Coverage Δ
testing/test_junitxml.py 97.87% <100%> (+0.03%) ⬆️
src/_pytest/junitxml.py 95.63% <100%> (+0.38%) ⬆️

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 f5c1f3d...8f23e19. Read the comment docs.

"property" elements cannot be children of "testsuite" according to the schema, so it is incompatible with xunit2

Related to pytest-dev#5202
@nicoddemus nicoddemus merged commit 4a2fdce into pytest-dev:features May 6, 2019
@nicoddemus nicoddemus deleted the record-property-xunit2 branch May 6, 2019 00:33
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