Skip to content

junit: allow multiple properties with same name #1423

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
merged 1 commit into from
Feb 29, 2016

Conversation

lukas-bednar
Copy link
Contributor

It might happen that test can be affected by two or more bugs.
I need to be able to track them all.

Fix #1422

It might happen that test can be affected by two or more bugs.
I need to be able to track them all.
@RonnyPfannschmidt
Copy link
Member

looks good to merge, is there a special reason why both, properties and the insert-order is needed?

i wonder if the changes section might be a better place in the changelog

@The-Compiler
Copy link
Member

LGTM, but I'm not familiar with that part of the code and JUnit - so I'll leave this one to @RonnyPfannschmidt, @nicoddemus or anyone else who feels inclined 😉

@dajose - could you give this a look as well?

(Heh, I just managed to mention @lukas-bednar as well, then noticed you're the author. Sorry, it's Monday! 😆)

@@ -98,7 +98,8 @@
(auto/long/short/line/native/no), with `auto` being the default since v2.6.
Thanks `@hackebrot`_ for the PR.

*
* Fix (`#1422`): junit record_xml_property doesn't allow multiple records
Copy link
Contributor Author

Choose a reason for hiding this comment

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

ops, will append underscore

@nicoddemus
Copy link
Member

LGTM as well! 😄

Once it passes on CI we can merge it.

nicoddemus added a commit that referenced this pull request Feb 29, 2016
junit: allow multiple properties with same name
@nicoddemus nicoddemus merged commit 5c09b33 into pytest-dev:master Feb 29, 2016
@lukas-bednar lukas-bednar deleted the junit_properties branch March 1, 2016 08:06
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.

4 participants