Re: [jbehave-user] Story duration are not calculated correctly in multi-thread execution

[Mauro Talevi]

Not sure what you mean.   Where do you want to make available the story 
durations?

On 20/03/2015 00:17, tran, phong wrote:

Thanks Mauro and Brent for confirming the fix. It’s actually my fault. 
I did not update all other modules in the project with the latest 
JBehave 3.9.5. I could see the storyDurations.props file created with 
expected story duration time now. My next question is how I can take 
the information in storyDurations.props file and make them available 
for access in the FreeMarker templates (.ftl) to produce the HTML views?

Thanks,

Phong

*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Thursday, March 19, 2015 3:00 AM
*To:* user@jbehave.codehaus.org
*Subject:* Re: [jbehave-user] Story duration are not calculated 
correctly in multi-thread execution

Can you provide a sample project reproducting this behaviour.

This problem should be fixed in latest release.

On 17/03/2015 22:39, tran, phong wrote:

    When I ran stories with a single thread (serial), the story
    duration in reports looked correct. The duration time is in
    minutes as expected. See the attached report
    (single-thread-reports.png). However, when stories are executed
    with multiple threads (currently), the story duration is not
    calculated correctly (See Multiple-Thread-Reports.png). The
    duration time is in in sub-seconds and is not what expected. I’m
    using JBehave 3.9.2 and thought this problem could be related to
    https://jira.codehaus.org/browse/JBEHAVE-1041 but upgrading to the
    latest JBehave 3.9.5 does not seem to help with this problem.

    Here is the code fragment for building story report.

    .useStoryReporterBuilder(new StoryReporterBuilder()

                    .withDefaultFormats()

                    .withFormats(CONSOLE, TXT, HTML_WEB)

                    .withFailureTrace(true)

    .withFailureTraceCompression(false)

    .withViewResources(viewResources)

                    .withCrossReference(xref)

                    );

    Does anyone have an idea what’s could be the problem here?

    Thanks in advance,

    Phong




      

    ---------------------------------------------------------------------

    To unsubscribe from this list, please visit:

      

         http://xircles.codehaus.org/manage_email