I was asking about the issue I had mentioned date-Mon, Jul 15, 2013 as provided the sample project as well. So, will your answer still be same i.e The issue has been identified and will be addressed as part of the development cycle? Please advice.
On Tue, Jul 16, 2013 at 1:13 PM, Mauro Talevi <mauro.tal...@aquilonia.org>wrote: > What update are you expecting? The issue has been identified and will > be addressed as part of the development cycle. > > Please create a JIRA issue affecting version 4.0 and attach the project to > it. > > > On 16/07/2013 07:55, Selenium Learner 2013 wrote: > > Is there any update on the issue I had mentioned in my previous > mails?Please advice. > > > On Mon, Jul 15, 2013 at 9:09 PM, Selenium Learner 2013 < > 777selen...@gmail.com> wrote: > >> Attached is the sample project. >> >> >> On Mon, Jul 15, 2013 at 8:59 PM, Selenium Learner 2013 < >> 777selen...@gmail.com> wrote: >> >>> the reason , I have attached sample project in the previous mail can be >>> seen below.. >>> >>> >>> Ok, thanks.Sorry for the late reply as was busy creating different >>> sample project so that multithreading issue can be addressed again. >>> Attached is the new sample project(took from Git hub again and made >>> some changes).I have observed couple of issues: >>> 1) If I make thread value as 2 in POM .xml, I could not see two >>> instances of Firefox when I type mvn clean install in the command promt >>> ..is there any problem at Jbehave end? Please advice. >>> 2) For this project,I doubt report generation will happen correctly but >>> because of issue 1.. >>> Is there any problem in Jbehave if a user try to use selenium >>> configuration rather than most useful configuration?Please advice >>> >>> Let me know in case of any queries. >>> >>> >>> On Mon, Jul 15, 2013 at 8:55 PM, Selenium Learner 2013 < >>> 777selen...@gmail.com> wrote: >>> >>>> >>>> FYI...as previous mail got bounced.. >>>> ---------- Forwarded message ---------- >>>> From: Selenium Learner 2013 <777selen...@gmail.com> >>>> Date: Mon, Jul 15, 2013 at 8:53 PM >>>> Subject: Re: [jbehave-dev] multithreading reporting is not working >>>> To: dev@jbehave.codehaus.org >>>> >>>> >>>> Ok, thanks.Sorry for the late reply as was busy creating different >>>> sample project so that multithreading issue can be addressed again. >>>> Attached is the new sample project(took from Git hub again and made >>>> some changes).I have observed couple of issues: >>>> 1) If I make thread value as 2 in POM .xml, I could not see two >>>> instances of Firefox when I type mvn clean install in the command promt >>>> ..is there any problem at Jbehave end? Please advice. >>>> 2) For this project,I doubt report generation will happen correctly >>>> but because of issue 1.. >>>> Is there any problem in Jbehave if a user try to use selenium >>>> configuration rather than most useful configuration?Please advice >>>> >>>> Let me know in case of any queries. >>>> >>>> >>>> On Fri, Jul 12, 2013 at 2:18 PM, Mauro Talevi < >>>> mauro.tal...@aquilonia.org> wrote: >>>> >>>>> Yes, issue reporting on preview version is most welcome. >>>>> >>>>> >>>>> On 11 Jul 2013, at 14:46, Selenium Learner 2013 <777selen...@gmail.com> >>>>> wrote: >>>>> >>>>> So, can I conclude that for 4.x it's not working and I can report >>>>> the issues related to execution and reporting pipework? Please advice. >>>>> >>>>> >>>>> >>>>> >>>>> On Thu, Jul 11, 2013 at 1:34 PM, Mauro Talevi < >>>>> mauro.tal...@aquilonia.org> wrote: >>>>> >>>>>> You're using a preview version 4.0-beta-1. It works fine with >>>>>> latest stable release 3.8. >>>>>> >>>>>> Please stay on stable version unless you have a reason not to. By >>>>>> all means you're encouranged to try it and report issues, but be aware >>>>>> that >>>>>> the 4.x release has significant changes on the execution and reporting >>>>>> pipework. >>>>>> >>>>>> On 10/07/2013 17:23, Selenium Learner 2013 wrote: >>>>>> >>>>>> Attached is the sample project to reproduce the problem. I am >>>>>> looking output report file in the path/location >>>>>> :-/target/jbehave/view/reports.html. >>>>>> >>>>>> In above output file, I could see report been generated for >>>>>> Team1.story correctly as for Team.story all numbers are seen as 0 in the >>>>>> report when running in multithreading mode. >>>>>> Is there any Jbehave architecture bug present ? Please suggest. >>>>>> >>>>>> It's happening when running stories via IDE(Eclipse) or command >>>>>> promy(maven - mvn integration-test) i.e in both ways. >>>>>> >>>>>> Let me know in case of any questions. >>>>>> >>>>>> >>>>>> Regards, >>>>>> Selenium-777 >>>>>> >>>>>> >>>>>> On Tue, Jul 9, 2013 at 9:58 PM, Mauro Talevi < >>>>>> mauro.tal...@aquilonia.org> wrote: >>>>>> >>>>>>> As already repeated, we can only help if you provide a project >>>>>>> that reproduces the problem. >>>>>>> >>>>>>> On 9 Jul 2013, at 13:03, Selenium Learner 2013 < >>>>>>> 777selen...@gmail.com> wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> My problem is that even though stories could run on parallel basis >>>>>>> but when report got generated I could not see correct reports. >>>>>>> I have used the similar structure used in >>>>>>> https://github.com/jbehave/jbehave-core/tree/master/examples/threads >>>>>>> >>>>>>> But when reports are generated they are not proper i.e story >>>>>>> reports are seen overlapping hence can't judge which story got >>>>>>> successful >>>>>>> etc.. >>>>>>> Any idea why its happening? >>>>>>> I debug into jbehave source code and found that under the package >>>>>>> package org.jbehave.core.reporters; there is one class >>>>>>> ConcurrentStoryReporter which might solve the problem but don't know >>>>>>> which >>>>>>> method I should use under my configuration..could any dev help on this >>>>>>> issue? Somehow this ConcurrentStoryReporter class has not being used >>>>>>> for >>>>>>> /examples/threads<https://github.com/jbehave/jbehave-core/tree/master/examples/threads>..is >>>>>>> there any specific reason? Please advice >>>>>>> >>>>>>> My reports are generated under \targe\jbehave\view . >>>>>>> >>>>>>> Regards, >>>>>>> Selenium-777 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> > >
