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

Wrong display of jbehave tests in error #2

Closed
Zinovios opened this issue Feb 2, 2011 · 2 comments
Closed

Wrong display of jbehave tests in error #2

Zinovios opened this issue Feb 2, 2011 · 2 comments

Comments

@Zinovios
Copy link

Zinovios commented Feb 2, 2011

Maybe it is a request rather than an issue. Sorry if I posted at the wrong place.

In my project, I've just one JUnitStories test executing all be JBehave stories.

So when I display my project test reports in hudson, it shows a classic graph showing evolution of successful and unsuccessful JUnit tests in error, and in my case it just on error if my JUnitStories test returns an error (if one scenario failed) or not (if all scenarii ran successfully).
But my JUnitStories test contains several stories and each story contains several scenarii, so I wish to display which scenarii are in error or which stories are in error.
I would also happy if the number of stories (or scenarii) in error was displayed in hudson overview tab.

Is that could be done easily ?

Regards,

@aparkinson
Copy link
Owner

Hi

This problem has only been logged in the JBehave JIRA in the last few days.

The in depth explanation is located here: https://github.com/aparkinson/jbehave-hudson-plugin/issues#issue/2

The key problem is two test reports being generated. One way to avoid this problem is not to execute the tests using junit, I'm using the jbehave maven plugin's "run-stories-as-paths" goal to run my tests.

The other alternative is to a create new “free-style” hudson project (not a maven 2/3 project) and set up maven to build within this new project. “free-style” projects don't use the code in Hudson that cause the problem.

FYI I'm investigating writing a new plugin but it will take some time to investigate.

Regards,

Alan

@Zinovios
Copy link
Author

Zinovios commented Feb 3, 2011

This issue was in fact linked to the resolved issue 1 so I close it. Thanks for your explanations.

Regards,
Marc

This issue was closed.
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

No branches or pull requests

2 participants