|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
[jbehave-dev] [jira] (JBEHAVE-551) Better integration with JUnit (Separate results for each story/scenario/example)
Andreas Ebbert-Karroum (JIRA) Sun, 26 Aug 2012 14:04:24 -0700
- [jbehave-dev] [jira] (JBEHAVE-551) Better in... Andreas Ebbert-Karroum (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-551) Bett... Sergey (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-551) Bett... joachim nilsson (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-551) Bett... joachim nilsson (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-551) Bett... Andreas Ebbert-Karroum (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-551) Bett... Sebastien Tardif (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-551) Bett... Simon Zambrovski (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-551) Bett... Simon Zambrovski (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-551) Bett... Simon Zambrovski (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-551) Bett... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-551) Bett... Mauro Talevi (JIRA)
Joachim, thanks for Your support of jbehave-junit-runner. I'd love to implement the jump to the story file, when you click on the JUnit result, but to the best of my knowledge this is not possible. This limitation is a combination of JUnit and usual IDE integrations, like in Eclipse. In JUnit you can only remember, which method and class a test belongs to. The IDE integration then allows you to jump to that method in a class. If you have any idea, how to circumvent these challenges, I welcome your ideas![]()