Any update on above issue?Please advice



On Wed, Jul 10, 2013 at 9:53 PM, Selenium Learner 2013 <
777selen...@gmail.com> 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
>>
>>
>

Reply via email to