|
||||||||
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-808) PostStoryStatistics... James Shaw (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) PostStoryStati... James Shaw (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) PostStoryStati... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) PostStoryStati... James Shaw (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) PostStoryStati... James Shaw (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) PostStoryStati... James Shaw (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) Add timings to... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) Add timings to... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) Add timings to... James Shaw (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) Add timings to... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) Add timings to... James Shaw (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) Add timings to... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-808) Add timings to... Mauro Talevi (JIRA)
Having looked a bit more, I think this is happening because ConcurrentStoryReporter is deferring execution of the StoryReporters until after the story has executed.
I have a couple of ideas:
1) Implement timing of stories in a similar way to CrossReference's durationInMillis for invidual steps: make PerformableStory save a StoryResults object that would be serialised by CrossReference
2) Provide a way deferring execution of only some StoryReporters. Then make PostStoryStatisticsCollector thread safe as you suggested
Any further thoughts?