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

Add ability to set suite name in JUnit XML report #533

Closed
pytestbot opened this issue Jun 26, 2014 · 4 comments
Closed

Add ability to set suite name in JUnit XML report #533

pytestbot opened this issue Jun 26, 2014 · 4 comments

Comments

@pytestbot
Copy link
Contributor

@pytestbot pytestbot commented Jun 26, 2014

Originally reported by: Simon Lundmark (BitBucket: simlun, GitHub: simlun)


Today as of the resolved issue #355 the XML report's root <testsuite> tag's name attribute is hard-coded to pytest. To make reporting easier in larger projects with several test suites it is useful to set this attribute to something meaningful like unit, integration, gui, etc. Other reporting tools that read and aggregate JUnit-style XML reports rely on this argument.

I propose adding a --junit-suitename str argument to the py.test command which would set this string.

I'm happy to contribute to the project with this feature if the people in charge think it's a good idea.


@pytestbot
Copy link
Contributor Author

@pytestbot pytestbot commented Sep 10, 2014

Original comment by Simon Lundmark (BitBucket: simlun, GitHub: simlun):


What do you say @hpk42 ? Is this feature likely to be included in pytest if the code were to be written? Or is it better to build this as some kind of plugin?

Loading

@pytestbot
Copy link
Contributor Author

@pytestbot pytestbot commented Sep 10, 2014

Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):


Sorry for failing to get back -- yes, i think this is a useful feature. See http://pytest.org/latest/contributing.html for more info how to proceed.

Loading

@pytestbot
Copy link
Contributor Author

@pytestbot pytestbot commented Sep 10, 2014

Original comment by Simon Lundmark (BitBucket: simlun, GitHub: simlun):


No worries, thanks for your (now very quick 😃) reply! I will read up on contributing!

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants