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

JUnit formatter, classname contains only the features name #193

Merged
merged 1 commit into from Apr 24, 2012

Conversation

litvinok
Copy link
Contributor

@litvinok litvinok commented Dec 2, 2011

In the testcase attribute name is the name of the test and classname of his group, which is often similar to the attribute name block testsuite.

@hron84
Copy link

hron84 commented Feb 19, 2012

-1 If i use one feature with more scenarios, it is good if if is put to separated file.

@mattwynne
Copy link
Member

@hron84 I don't understand your objection - this looks like a reasonable way to use the JUnit file format, isn't it?

What would you lose if we merged in this patch?

@hron84
Copy link

hron84 commented Apr 23, 2012

@mattwynne ohh, I missed some points, I thought Jenkins flattens all tests under simple classes, but it was a mistake.

However, the current workflow is good for me because I don't need to scroll if I have a lot of scenario in a feature test. I have a cmdline JUnit XML parser to be able to run tests in same environment as Jenkins does to avoid failing tests caused by config difference.

However, if it really makes sense, I can agree it ,as because my main argument is not valid.

mattwynne added a commit that referenced this pull request Apr 24, 2012
JUnit formatter, classname contains only the feature's name
@mattwynne mattwynne merged commit b940a29 into cucumber:master Apr 24, 2012
@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants