[jbehave-dev] [jira] (JBEHAVE-1077) Archetypes featuring a StepMonitor with JFrameContextView
Title: Message Title Mauro Talevi commented on an issue Re: Archetypes featuring a StepMonitor with JFrameContextView Sure, that's a good idea! Please provide a pull request. Add Comment JBehave / JBEHAVE-1077 Archetypes featuring a StepMonitor with JFrameContextView What about adding the nice JFrameContextView in all of the archetypes? I've started with the archetype simple. If you like the idea, I can add it to all. https://github.com/alb-i986/jbehave-core/tree/archetypes-with-step-monitor This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time
Title: Message Title Mauro Talevi commented on an issue Re: Provide a configurable timeout value for each story running time Hi Christopher, thanks for the update. I'm quite puzzled by the difference between Maven and Ant. The logic of the timeout matching is entirely external to either, being in the StoryManager. Can you offer more information or a reproduceable example? As for the behaviour in presence of slashes, could you please see if you can reproduce at unit level in the StoryManagerBehaviour? Add Comment JBehave / JBEHAVE-833 Provide a configurable timeout value for each story running time When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1036) StoryReporterBuilder fails to parse test results if story has GivenStories
Title: Message Title Mauro Talevi resolved an issue as Fixed Pulled with thanks JBehave / JBEHAVE-1036 StoryReporterBuilder fails to parse test results if story has GivenStories Change By: Mauro Talevi Resolution: Fixed Fix Version/s: 4.0 Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time
Title: Message Title Mauro Talevi commented on an issue Re: Provide a configurable timeout value for each story running time Hi Christopher, I've committed a fix to support both ant-style patterns (a la StoryFinder) and regex patterns. I've also updated the core examples pom.xml with story timeouts. Can you please give it a whirl and let me know if we can resolve this issue? Add Comment JBehave / JBEHAVE-833 Provide a configurable timeout value for each story running time When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time
Title: Message Title Mauro Talevi commented on an issue Re: Provide a configurable timeout value for each story running time Hi Christopher, you can set it either in CoreStories or in the pom.xml but be aware that the pom.xml overrides what is set in the embedded Java configuration. Add Comment JBehave / JBEHAVE-833 Provide a configurable timeout value for each story running time When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1076) Travis builds failing
Title: Message Title
Mauro Talevi commented on an issue
Re: Travis builds failing
The jenkins maven repo is only for Jenkins artifacts. The surefire plugin is found in Maven Central. If not found in one repo, it'll look it up in another.
The build works with settings.xml provided unless there are network issues preventing correct download.
Travis has been known to have connection issues.
Add Comment
JBehave / JBEHAVE-1076
Travis builds failing
From my findings, it looks like the problem is the settings.xml file. E.g. this works - https://travis-ci.org/alb-i986/jbehave-core/builds/57723534 this does not - https://travis-ci.org/alb-i986/jbehave-core/builds/57725840 The latter fails because of these: {code} [WARNING] Could not validate integrity of download from http://maven.jenkins-c...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1075) Add FluentEnumConverter, able to convert lower-cased, space-separated values to Enums
Title: Message Title Mauro Talevi resolved an issue as Fixed Pulled with thanks JBehave / JBEHAVE-1075 Add FluentEnumConverter, able to convert lower-cased, space-separated values to Enums Change By: Mauro Talevi Resolution: Fixed Fix Version/s: 3.10 Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1075) Add FlexibleEnumConverter, able to convert lower-cased, space-separated values to Enums
Title: Message Title
Mauro Talevi commented on an issue
Re: Add FlexibleEnumConverter, able to convert lower-cased, space-separated values to Enums
I think FluentEnumConverter would be a more suitable name.
Add Comment
JBehave / JBEHAVE-1075
Add FlexibleEnumConverter, able to convert lower-cased, space-separated values to Enums
Copyingpasting from the javadoc: An EnumConverter allowing stories prose to be more natural. Before performing the actual conversion, it transforms values to upper-case, with any non-alphanumeric character replaced by an underscore ('_'). Example: assuming we have defined the step Given I am on the $page which is mapped to the method iAmOnPage(Pa...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time
Title: Message Title Mauro Talevi commented on an issue Re: Provide a configurable timeout value for each story running time I think it'd be much easier to modifiy the examples' CoreStories configuration to reproduce the behaviour in the doc. Can you provide such pull request please? I'd be interested in understanding what works and what does not for you. Thanks Add Comment JBehave / JBEHAVE-833 Provide a configurable timeout value for each story running time When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1066) Upgrade dependencies to support JDK 8
Title: Message Title Mauro Talevi resolved an issue as Fixed JBehave / JBEHAVE-1066 Upgrade dependencies to support JDK 8 Change By: Mauro Talevi Resolution: Fixed Status: InProgress Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1073) Story duration time in multi-threading execution mode is higher than normal
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1073 Story duration time in multi-threading execution mode is higher than normal Change By: Mauro Talevi Fix Version/s: 3.9.6 Assignee: MauroTalevi From:MauroTalevi[mailto:mauro.tal...@aquilonia.org]Sent:Wednesday,April01,20154:03PMTo:u...@jbehave.codehaus.orgSubject:Re:[jbehave-user]Storydurationarenotcalculatedcorrectlyinmulti-threadexecutionSure,easyenoughtodo!CanyoupleaseraiseaJIRAissueforthisusecase?CheersOn1Apr2015,at23:56,tran,phongphong.t...@emc.comwrote:HiMauro,Yeswere When runninginmulti-threadingmode with10threadsforconcurrentstoryexecution.EmbedderControls[batch=false , skip=false,generateViewAfterStories=true,ignoreFailureInStories=true,ignoreFailureInView=false,verboseFailures=true,verboseFiltering=false,storyTimeoutInSecs=108000,failOnStoryTimeout=false,threads=10]Weretryingtospeedup the testexecution(Selenium-basedtests)withmultiplethreads(threads=10)targetingaSeleniumGridwith10nodes.Inoticedthatthereporteddurationforeachstoryisalsohighandthatiswhythesumofallstorydurationsaddeduptoahigh total number.Doesthismeanthedurationatthestorylevelhasbeenaffectedwithmulti-threadingexecutionmode?Doweneedtode-normalize(dividedby10inthiscase)thedurationforeachstorytogetitsaccurateexecutiontime?Itwouldbegreatifthede-normalizationforstorydurationcanbeataddressedattheJBehaveframeworkleveltohandlethemulti-threadingexecutionmode.Thanks,PhongFrom:MauroTalevi[mailto:mauro.tal...@aquilonia.org]Sent:Saturday,March28,20151:56AMTo:u...@jbehave.codehaus.orgSubject:Re:[jbehave-user]Storydurationarenotcalculatedcorrectlyinmulti-threadexecutionHiPhong,Iwouldimagineyou'rerunninginmulti-threadingmode.Thetotal iscalculatedassimplybethesumofeachduration.Ifyouhaveasinglethreadthenitwillcoincidewiththebuildduration(moreorless),butyouusemultiplethreadsit'llbeoffbyafactorwhichshouldcorrespondtothenumberofthreads. Arguablywecouldusetheinformationofthethreadstorenormalisethetotalbythenumberofthreads.Thisformulawouldstillworkinthecaseofasinglethread.Canyouconfirmthatyou'reusingmultiplethreads?CheersOn25/03/201508:22,tran,phongwrote:HiMauro,Thanksalotforupdatingthecoreexampletemplate!WecanaccessandintegratethedurationsfromstoryDurations.propsintoourcustomHTMLreportnow.However,wejustnoticeanotherissue.ThetotaldurationreportedinstoryDurations.propsforallstoriesismuchhigher(8times)thatwhatweusuallyseeinourtestrun.BasicallywehaveaconfigurationinTeamCitytorunourSelenium-basedtestsandthetestruntook5hoursand25minutesasreportedbyTeamCity.Thisisthenormaltimerangeweexpectedforourtestrun. Results Started Changes Started Duration #177 image001.pngNGIS#:6234Beacon#:3224PassRate:83.43949%passed:262failed:52pending:51 image002.pngView Changes(7) 24Mar1509:55 5h:25m Beacon_Selenium_W2K8R2_13 None
[jbehave-dev] [jira] (JBEHAVE-1073) Story duration time in multi-threading execution mode is higher than normal
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1073 Story duration time in multi-threading execution mode is higher than normal Change By: Mauro Talevi Summary: Storydurationtimeinmulti-threadingexecutionmodeis high higher thannormal Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1073) Story duration time in multi-threading execution mode is higher than normal
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1073 Story duration time in multi-threading execution mode is higher than normal Change By: Mauro Talevi Issue Type: Bug Improvement Whenrunninginmulti-threadingmode,thetotaliscalculatedassimplybethesumofeachduration.Ifyouhaveasinglethreadthenitwillcoincidewiththebuildduration(moreorless),but if youusemultiplethreadsit'llbeoffbyafactorwhichshouldcorrespondtothenumberofthreads. Theadditionalinformationoftheaveragedurationperthread,thetotalsumofthestorydurationsdividedbythenumberofthreads,shouldalsobeavailableifyouareinmulti-threadingmode. Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1072) Upgrade to Selenium 2.44.0
Title: Message Title Mauro Talevi created an issue JBehave / JBEHAVE-1072 Upgrade to Selenium 2.44.0 Issue Type: Task Assignee: Mauro Talevi Components: Web Selenium Created: 29/Mar/15 10:09 AM Fix Versions: web-3.6 Priority: Major Reporter: Mauro Talevi Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[jbehave-dev] [jira] (JBEHAVE-1071) Migrate from Codehaus Nexus to Sonatype Nexus
Title: Message Title Mauro Talevi created an issue JBehave / JBEHAVE-1071 Migrate from Codehaus Nexus to Sonatype Nexus Issue Type: Task Assignee: Mauro Talevi Components: Build Created: 21/Mar/15 9:10 AM Fix Versions: 3.9.6, 4.0 Priority: Critical Reporter: Mauro Talevi As Codehaus is closing down, use Sonatype OSS Nexus at https://oss.sonatype.org for releases and snapshots. Add Comment
[jbehave-dev] [jira] (JBEHAVE-362) Convert story name in report to human readable form
Title: Message Title Mauro Talevi commented on an issue Re: Convert story name in report to human readable form Please use mailing lists for these kind of questions (http://jbehave.org/mailing-lists.html). Do not comment on old resolved issues. Add Comment JBehave / JBEHAVE-362 Convert story name in report to human readable form Another good suggestion from feedback. Convert: - trader_sells_stocks.story - Trader Sells Stocks This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time
Title: Message Title Mauro Talevi commented on an issue Re: Provide a configurable timeout value for each story running time You're mixing two very different concerns here, configuration and monitoring. What matters is whether the path of the story we're running matches the regex patterns provided in the CSV of story timeouts. I'm looking into simplify your solution. Add Comment JBehave / JBEHAVE-833 Provide a configurable timeout value for each story running time When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1070) Loose step matching, not based on StepType
Title: Message Title
Mauro Talevi commented on an issue
Re: Loose step matching, not based on StepType
While it's true that this constraint is strictly speaking not needed, it is nonetheless useful as it forces scenario writers not to be lazy and think about the syntax and how to word the steps. It is rather unlikely that steps of different types have exactly the same syntax. One could argue that it's a smell.
That said, there are situations where that may happen. In this case it may be worth introducing an ANY value in the StepType enum (rather than dropping the step type).
Having an annotation @Step(type=ANY) could be a good suggestion. We could then also have @Step(type=GIVEN) as an alias to @Given, etc ...
Add Comment
JBehave / JBEHAVE-1070
Loose step matching, not based on StepType
Hi, I've recently started working with jbehave, and I am noticing duplication when a step method can be more than one StepType, e.g.: {code} @Given(the cart is empty) @When(the cart is empty) public void cartIsEmpty() {} {code} An easy (?) workaround could be to support the following syntax {code} @Given(the cart is empty) @When p...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time
Title: Message Title Mauro Talevi commented on an issue Re: Provide a configurable timeout value for each story running time Hi Christopher, finally got around to the patch. Can you please explain why you need to introduce the method public String getSearchDirectory() in the EmbedderMonitor? Add Comment JBehave / JBEHAVE-833 Provide a configurable timeout value for each story running time When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time
Title: Message Title
Mauro Talevi edited a comment on an issue
Re: Provide a configurable timeout value for each story running time
HiChristopher,finallygotaroundtothepatch.Canyoupleaseexplainwhyyouneedtointroducethemethod{code}publicStringgetSearchDirectory(){code}intheEmbedderMonitor? Ifyouneedtoconfigureanything,itshouldnotbeinthemonitorclass.
Add Comment
JBehave / JBEHAVE-833
Provide a configurable timeout value for each story running time
When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time
Title: Message Title Mauro Talevi commented on an issue Re: Provide a configurable timeout value for each story running time Hi Christopher, yes, I've seen it thanks. I'll get to it by the end of this week. Cheers Add Comment JBehave / JBEHAVE-833 Provide a configurable timeout value for each story running time When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1067) it is not possible to comment a scenario with !--
Title: Message Title Mauro Talevi commented on an issue Re: it is not possible to comment a scenario with !-- No, it's not possible to comment a scenario with !-- If you want to skip the execution of a scenario, you should annotated it with a meta property, e.g.: Scenario: Meta: @skip And use a filter -skip to avoid running the scenarios annotated with this property. Add Comment JBehave / JBEHAVE-1067 it is not possible to comment a scenario with !-- If you write a scenario with parameter see example, and comment the next scenario with !--. Then the previous when doesn't work. Example: This will not work Scenario: example When using profiles |profile| |WEBSOCKET 1 | !-- Scenario: xxx The scenario example will not work, because he think that !-- Scenario: xxx is a parameter. But i... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1066) Upgrade dependencies to support JDK 8
Title: Message Title Mauro Talevi created an issue JBehave / JBEHAVE-1066 Upgrade dependencies to support JDK 8 Issue Type: Improvement Assignee: Mauro Talevi Components: Core, Scala Support Created: 13/Feb/15 3:08 AM Fix Versions: 3.9.6, 4.0 Priority: Major Reporter: Mauro Talevi Upgrade any dependencies to support JDK 8. Add Comment
[jbehave-dev] [jira] (JBEHAVE-1066) Upgrade dependencies to support JDK 8
Title: Message Title Mauro Talevi started work on an issue Change By: Mauro Talevi Status: Open InProgress Add Comment JBehave / JBEHAVE-1066 Upgrade dependencies to support JDK 8 Upgrade any dependencies to support JDK 8. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1053) Allow entire story to be restarted
Title: Message Title Mauro Talevi commented on an issue Re: Allow entire story to be restarted Hi Brett, apologies for the delay in pulling this request. I meant to do the corresponding changes to the 4.x branch but did not get time for it. Could you perhaps have a first stab at it? Essentially changing the PerformableTree in a similar way you've modified the StoryRunner? Cheers Add Comment JBehave / JBEHAVE-1053 Allow entire story to be restarted For selenium tests that keep the same browser / context throughout the story, there are countless things that can go wrong such as network latency, slow application, etc. Since a false positive can cause people to quickly lose trust in the tests, others advised that the story should restart x amount of times before failing the test. There is a way to... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1065) error with tab character in comments
Title: Message Title Mauro Talevi commented on an issue Re: error with tab character in comments Could you please provide some concrete examples? As a side note, why not simply configure your editor to replace tabs with spaces? Add Comment JBehave / JBEHAVE-1065 error with tab character in comments When we write scenarios, we use tab character to aline columns of tabulars. The problem appears when such step is commented (entirely or partially) by prefixing each step line by !-- . The problem comes from the tab characters used in step tabular. The result is that next uncommented step is recognized pending, and thus scenario fails. If tab ch... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1053) Allow entire story to be restarted
Title: Message Title Mauro Talevi commented on an issue Re: Allow entire story to be restarted Hi Brett, the changes are a bit tricky to track because they're spread over multiple commits. Could you please provide in a single commit the proposed changes since the pull of Nov 10? Thanks Add Comment JBehave / JBEHAVE-1053 Allow entire story to be restarted For selenium tests that keep the same browser / context throughout the story, there are countless things that can go wrong such as network latency, slow application, etc. Since a false positive can cause people to quickly lose trust in the tests, others advised that the story should restart x amount of times before failing the test. There is a way to... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1063) ConcurrentModificationException in CrossReference.outputFile()
Title: Message Title
Mauro Talevi commented on an issue
Re: ConcurrentModificationException in CrossReference.outputFile()
Which version are you using? Can you provide a sample project that reproduces this behaviour?
Add Comment
JBehave / JBEHAVE-1063
ConcurrentModificationException in CrossReference.outputFile()
When Tests are executed massivley multithreaded, from time to time a ConcurrentModificationException is thrown when JBehave tries to write a report-file. Trace: {code} java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:926) at java.util.HashMap$KeyIterator.next(HashMap.java:960) at com.thoughtwork...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1062) Named parameter values containing backslash and dollar characters cause side effects
Title: Message Title Mauro Talevi resolved an issue as Fixed Pulled with thanks! JBehave / JBEHAVE-1062 Named parameter values containing backslash and dollar characters cause side effects Change By: Mauro Talevi Resolution: Fixed Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1062) Named parameter values containing backslash and dollar characters cause side effects
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1062 Named parameter values containing backslash and dollar characters cause side effects Change By: Mauro Talevi Affects Version/s: 3.9.6 Affects Version/s: 3.x Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-979) Improve default report
Title: Message Title Mauro Talevi commented on an issue Re: Improve default report Hi, thanks for the contribution. It's been pulled and applied to both master and jbehave-4.x branches. A couple of minor further suggestions: do we need all the tablefilter*.js files or tablefilter_all_min.js? can we use lower capitalisation consistently? can we use white as the background color of the table header? Add Comment JBehave / JBEHAVE-979 Improve default report The current report suffers from lack of information. i'm working on a bit project and most of the people prefer the junit report provided on jenkins ci. i think that the default report should have more information regrading: * step failure - add full stacktrace and as much information as possible * step duration * filtering for the report table (ex... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[jbehave-dev] [jira] (JBEHAVE-1061) @BeforeScenario runs for every steps file that are instanciated
Title: Message Title Mauro Talevi commented on an issue Re: @BeforeScenario runs for every steps file that are instanciated All the methods annotated with @BeforeScenario will run before each scenario, regardless of which steps file the are contained in. Can you provide a sample project reproducing your behaviour? Add Comment JBehave / JBEHAVE-1061 @BeforeScenario runs for every steps file that are instanciated When i run my scenario that are using multiple steps files, the method that are annotated with @BeforeScenario runs for each steps file. Im excpecting it to only run per scenario not per steps file This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time
Title: Message Title Mauro Talevi commented on an issue Re: Provide a configurable timeout value for each story running time This features requires two main elements: configuration: add a configuration element similar to storyTimeoutInSecs, which we may call storyTimeoutInSecsByPath, which will override the default value in storyTimeoutInSecs, and can be expressed as a CSV of regex expressions matching story paths. E.g. */long/.story:5000,*/short/.story:200. Note that there are several places where the storyTimeoutInSecs is configured and an equivalent element needs to be added for storyTimeoutInSecsByPath (using the type String in place of long). implementation of logic: in StoryManager the story timeouts by paths need to be parsed and matched according to the story path being executed Add Comment JBehave / JBEHAVE-833 Provide a configurable timeout value for each story running time When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time
Title: Message Title Mauro Talevi commented on an issue Re: Provide a configurable timeout value for each story running time To subscribe to the mailing lists you need to create a Codehaus account and then subscribe via the project site: http://xircles.codehaus.org/projects/jbehave Add Comment JBehave / JBEHAVE-833 Provide a configurable timeout value for each story running time When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-933) timeout should be applied to stories only
Title: Message Title Mauro Talevi commented on an issue Re: timeout should be applied to stories only Yes Add Comment JBehave / JBEHAVE-933 timeout should be applied to stories only Hi, as I read the specification of a timeout, it is setting the controls to let a story time out, when a specified amount of time has passed. By the name this is a setting per story. So, when I have a timeout of 300s per story, I should be able to have 100 stories, which take 250 seconds each. The way it is implemented is different, though. The Sto... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time
Title: Message Title Mauro Talevi commented on an issue Re: Provide a configurable timeout value for each story running time No, there is currently only one configured timeout value. Add Comment JBehave / JBEHAVE-833 Provide a configurable timeout value for each story running time When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1058) Hungarian language support
Title: Message Title Mauro Talevi resolved an issue as Fixed Pulled https://github.com/jbehave/jbehave-core/pull/70 with thanks JBehave / JBEHAVE-1058 Hungarian language support Change By: Mauro Talevi Resolution: Fixed Assignee: MauroTalevi Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1060) Polish language support
Title: Message Title Mauro Talevi resolved an issue as Fixed Pulled with thanks JBehave / JBEHAVE-1060 Polish language support Change By: Mauro Talevi Resolution: Fixed Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1060) Polish language support
Title: Message Title Mauro Talevi assigned an issue to Mauro Talevi JBehave / JBEHAVE-1060 Polish language support Change By: Mauro Talevi Assignee: MauroTalevi Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1059) NPE during run tests in other languages
Title: Message Title
Mauro Talevi commented on an issue
Re: NPE during run tests in other languages
This NPE does not occur in the JBehave code but in the codecentric code.
You should raise the issue with them.
Add Comment
JBehave / JBEHAVE-1059
NPE during run tests in other languages
I have a simple project Jbehave + Thucydides from archetype: net.thucydides:thucydides-jbehave-archetype. And I modified class *de.jbehave.AcceptanceTestSuite* to change the locale of the test for other language e.x. German {code:lang=java} package de.jbehave; import net.thucydides.jbehave.ThucydidesJUnitStories; import net.thucydides.jbehave.UTF8S...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1058) Hungarian language support
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1058 Hungarian language support Change By: Mauro Talevi Fix Version/s: 3.9.6 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1058) Hungarian language support
Title: Message Title Mauro Talevi commented on an issue Re: Hungarian language support Can you please provide a patch with the Hungarian version of keywords: https://github.com/jbehave/jbehave-core/blob/master/jbehave-core/src/main/resources/i18n/keywords_en.properties Add Comment JBehave / JBEHAVE-1058 Hungarian language support This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1056) ResolveToPackagedName path resolver is broken on Windows
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1056 ResolveToPackagedName path resolver is broken on Windows Change By: Mauro Talevi Affects Version/s: 3.x Affects Version/s: 3.9.5 Fix Version/s: 3.9.6 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1056) ResolveToPackagedName path resolver is broken on Windows
Title: Message Title
Mauro Talevi commented on an issue
Re: ResolveToPackagedName path resolver is broken on Windows
Could you please provide an example project reproducing this behaviour, in particular the configuration you use.
Add Comment
JBehave / JBEHAVE-1056
ResolveToPackagedName path resolver is broken on Windows
Current implementation of 'org.jbehave.core.reporters.FilePrintStreamFactory.ResolveToPackagedName' is the following: {code:java} public static class ResolveToPackagedName extends AbstractPathResolver { public String resolveName(StoryLocation storyLocation , String extension) { String name = storyLocation .getPath().replace...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1057) Jenkins plugin broken, unmatched dependency
Title: Message Title Mauro Talevi commented on an issue Re: Jenkins plugin broken, unmatched dependency The DTKit dependency comes from the Jenkins xunit plugin. Could you please try building the jbehave-jenkins-plugin with the latest updated version $ mvn clean install -Dxunit.plugin.version=1.92 to see if this fixes the problem? The currently used version of the xunit plugin is 1.62. Add Comment JBehave / JBEHAVE-1057 Jenkins plugin broken, unmatched dependency Current available jenkins plugin has unmatched dependency. When installing it crashes with: WARNING: Failed to load org.jBehavePluginType$DescriptorImpl jbehave is then not available in product configuration for processing the output. I'm not only one with this problem. Here is a workaround which works great, modified jenkins package without the ... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please
[jbehave-dev] [jira] (JBEHAVE-1055) FileNotFoundException storyDurations.props
Title: Message Title Mauro Talevi resolved an issue as Fixed JBehave / JBEHAVE-1055 FileNotFoundException storyDurations.props Change By: Mauro Talevi Resolution: Fixed Fix Version/s: 3.9.6 Assignee: MauroTalevi Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1054) Regression: configuration method inherited from JUnitStories class not being overridden
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1054 Regression: configuration method inherited from JUnitStories class not being overridden Change By: Mauro Talevi Fix Version/s: 3.9.2 Fix Version/s: 3.9.6 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1053) Allow entire story to be restarted
Title: Message Title Mauro Talevi commented on an issue Re: Allow entire story to be restarted Did some cleanup on the StoryRunner implementation. Can you please verify it works on your side? Please add any different behaviour to restarting.story. Add Comment JBehave / JBEHAVE-1053 Allow entire story to be restarted For selenium tests that keep the same browser / context throughout the story, there are countless things that can go wrong such as network latency, slow application, etc. Since a false positive can cause people to quickly lose trust in the tests, others advised that the story should restart x amount of times before failing the test. There is a way to... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1054) Regression: configuration method inherited from JUnitStories class not being overridden
Title: Message Title Mauro Talevi edited a comment on an issue Re: Regression: configuration method inherited from JUnitStories class not being overridden Yes,thisisasideeffectofJBEHAVE-1009.TheConfigurableEmbeddernowusestheconfiguration()methodlazilyonlyifthereisnootherconfigurationset.TooverridewithyourinstanceofConfiguration,youcanusethe#useConfiguration()methodintheconstructoroftheclassinheritingfromJUnitStories. TheCoreStoriesinthecoreexamplesshowhowtoconfigureusingtheconfiguration()method. Ifyoustillhaveproblems,pleaseprovideafullyworkingexamplebuildableandexecutablebycommand-line(eitheraziporagitrepo)sowecanreproduceyourbehaviour. Add Comment JBehave / JBEHAVE-1054 Regression: configuration method inherited from JUnitStories class not being overridden When creating a JUnitStories class, the overridden configuration method is no longer executed starting in JBehave 3.9.2. I also tested this with 3.9.3, 3.9.5 and 4.0-beta-11 and the issue persists. Only by changing the dependency version in my POM back to 3.9.1 does the method override correctly again. I have attached my StoryReporter class, the abs... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[jbehave-dev] [jira] (JBEHAVE-1054) Regression: configuration method inherited from JUnitStories class not being overridden
Title: Message Title Mauro Talevi commented on an issue Re: Regression: configuration method inherited from JUnitStories class not being overridden Incidentally, you seem to be using both the annotated embedder and extending JUnitStories (which extends the configurable embedder). Using the two is redundant and may lead to inconsistent behaviour. It should suffice to use one of the two. Add Comment JBehave / JBEHAVE-1054 Regression: configuration method inherited from JUnitStories class not being overridden When creating a JUnitStories class, the overridden configuration method is no longer executed starting in JBehave 3.9.2. I also tested this with 3.9.3, 3.9.5 and 4.0-beta-11 and the issue persists. Only by changing the dependency version in my POM back to 3.9.1 does the method override correctly again. I have attached my StoryReporter class, the abs... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1054) Regression: configuration method inherited from JUnitStories class not being overridden
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1054 Regression: configuration method inherited from JUnitStories class not being overridden You're using an inconsistent mix of version for the jbehave dependencies in your pom.xml. With the attached patch (i.e. using the same jbehave version for all dependencies) it picks up your configuration. Change By: Mauro Talevi Attachment: pom.patch Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1054) Regression: configuration method inherited from JUnitStories class not being overridden
Title: Message Title Mauro Talevi commented on an issue Re: Regression: configuration method inherited from JUnitStories class not being overridden Yes, this is a side effect of JBEHAVE-1009 . The ConfigurableEmbedder now uses the configuration() method lazily only if there is no other configuration set. To override with your instance of Configuration, you can use the #useConfiguration() method in the constructor of the class inheriting from JUnitStories. Add Comment JBehave / JBEHAVE-1054 Regression: configuration method inherited from JUnitStories class not being overridden When creating a JUnitStories class, the overridden configuration method is no longer executed starting in JBehave 3.9.2. I also tested this with 3.9.3, 3.9.5 and 4.0-beta-11 and the issue persists. Only by changing the dependency version in my POM back to 3.9.1 does the method override correctly again. I have attached my StoryReporter class, the abs... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[jbehave-dev] [jira] (JBEHAVE-1053) Allow entire story to be restarted
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1053 Allow entire story to be restarted Change By: Mauro Talevi Fix Version/s: 3.9.6 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1053) Allow entire story to be restarted
Title: Message Title Mauro Talevi commented on an issue Re: Allow entire story to be restarted Thanks for the contribution! I'll have a look at it soon. As for the multi-threading reporting, it should get reported by the invokeDelayed() method in the ConcurrentReporter. Add Comment JBehave / JBEHAVE-1053 Allow entire story to be restarted For selenium tests that keep the same browser / context throughout the story, there are countless things that can go wrong such as network latency, slow application, etc. Since a false positive can cause people to quickly lose trust in the tests, others advised that the story should restart x amount of times before failing the test. There is a way to... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1051) The method StoryManager.waitUntilAllDoneOrFailed(BatchFailures) can cancel un-started stories
Title: Message Title Mauro Talevi commented on an issue Re: The method StoryManager.waitUntilAllDoneOrFailed(BatchFailures) can cancel un-started stories You mean before the loop over the RunningStory collection, and not after? You think that 100ms would make such a difference? Add Comment JBehave / JBEHAVE-1051 The method StoryManager.waitUntilAllDoneOrFailed(BatchFailures) can cancel un-started stories I run several stories in parallel using the default multi-threaded Embedder.executorService and configure it with EmbedderControls.threads 1 Sometimes the JBEHAVE ends and no scenario (but before- and after- scenario) of my stories was even started. It is not repeatable, sometims it goes good. I founded out, that the method StoryManager.waitUntilAllDo... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1052) Upgrade Selenium version
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1052 Upgrade Selenium version Change By: Mauro Talevi Affects Version/s: web-3.5.5 Fix Version/s: web-3.6 Summary: JbehavesupportsfornewMozilla UpgradeSelenium version Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1052) Upgrade Selenium version
Title: Message Title Mauro Talevi commented on an issue Re: Upgrade Selenium version Please note you can always upgrade the selenium version via the Maven dependencyManagement/ section. Add Comment JBehave / JBEHAVE-1052 Upgrade Selenium version I am using Jbehave web 3.5.5 with Selenium 3.26.0 which in turn support till Mozilla v16. Could you please upgrade Jbehave web to support latest selenium webdriver and Mozilla versions. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1050) Last of two subsequent AND-clauses with translated keywords is not performed
Title: Message Title Mauro Talevi resolved an issue as Not A Bug You had two misconfigurations: 1. The i18n/keywords_ru.properties was not in the Maven classpath, masked by the (unnecessary) override of the resources 2. The StepCollector also needs to know about the keywords used. Please refer to the attached patch for a working version. PS: Note that JBehave is not yet tested with JDK 1.8. It should work but I've tested with 1.7. JBehave / JBEHAVE-1050 Last of two subsequent AND-clauses with translated keywords is not performed Change By: Mauro Talevi Resolution: NotABug Fix Version/s: 3.9.5 Assignee: MauroTalevi Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[jbehave-dev] [jira] (JBEHAVE-1051) The method StoryManager.waitUntilAllDoneOrFailed(BatchFailures) can cancel un-started stories
Title: Message Title Mauro Talevi resolved an issue as Duplicate Duplicate of JBEHAVE-1046. JBehave / JBEHAVE-1051 The method StoryManager.waitUntilAllDoneOrFailed(BatchFailures) can cancel un-started stories Change By: Mauro Talevi Resolution: Duplicate Fix Version/s: 3.9.5 Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1046) FailingUponPendingSteps strategy not honoured
Title: Message Title Mauro Talevi resolved an issue as Fixed Added examples/core/src/main/java/org/jbehave/examples/core/CoreStoriesFailingUponPending.java to verify behaviour. JBehave / JBEHAVE-1046 FailingUponPendingSteps strategy not honoured Change By: Mauro Talevi Resolution: Fixed Assignee: MauroTalevi Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1049) StepCreator doesn't support method generics parameters
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1049 StepCreator doesn't support method generics parameters Change By: Mauro Talevi Summary: StepCreatordoesn't takeType supportmethodgenerics parameters butClass?ofparameters Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1049) StepCreator doesn't support method generics parameters
Title: Message Title Mauro Talevi resolved an issue as Fixed JBehave / JBEHAVE-1049 StepCreator doesn't support method generics parameters Change By: Mauro Talevi Resolution: Fixed Assignee: MauroTalevi Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1048) Update toString() to show the system based values
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1048 Update toString() to show the system based values Change By: Mauro Talevi Fix Version/s: 4.x Fix Version/s: 3.9.5 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1048) Update toString() to show the system based values
Title: Message Title Mauro Talevi resolved an issue as Fixed Pulled with thanks JBehave / JBEHAVE-1048 Update toString() to show the system based values Change By: Mauro Talevi Resolution: Fixed Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1046) FailingUponPendingSteps strategy not honoured
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1046 FailingUponPendingSteps strategy not honoured Change By: Mauro Talevi Fix Version/s: 3.9.5 Summary: JBehaveexitsimmaturely FailingUponPendingStepsstrategynothonoured Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1045) Support for class-based AOP in step classes in Spring
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1045 Support for class-based AOP in step classes in Spring Change By: Mauro Talevi Affects Version/s: 4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1045) Support for class-based AOP in step classes in Spring
Title: Message Title Mauro Talevi resolved an issue as Fixed JBehave / JBEHAVE-1045 Support for class-based AOP in step classes in Spring Change By: Mauro Talevi Resolution: Fixed Fix Version/s: 3.9.5 Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1045) Support for class-based AOP in step classes in Spring
Title: Message Title Mauro Talevi commented on an issue Re: Support for class-based AOP in step classes in Spring Thanks for the pull request. It looks good at first sight. Will try to pull shortly. As for the test, you are right that it should not rely on the order. Add Comment JBehave / JBEHAVE-1045 Support for class-based AOP in step classes in Spring When I add @EnableAspectJAutoProxy in my spring setup, with the bundled steps factory, my step beans can't be found. I've done my own steps factory... it assumes the use of a specific type annotation on the step classes, to make it more clear which beans to explore, but that can be removed in a more general case. Here it's how it looks like (WIP): ... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1046) JBehave exits immaturely
Title: Message Title Mauro Talevi commented on an issue Re: JBehave exits immaturely Can you please provide an example of running stories not being started? The assumption is that at least one story has started. Otherwise, we can add a wait for at least one to start. Add Comment JBehave / JBEHAVE-1046 JBehave exits immaturely When I run a story, JBehave exits without waiting for the story results. The same stories work perfectly in version 3.9.3. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1045) Support for class-based AOP in step classes in Spring
Title: Message Title Mauro Talevi commented on an issue Re: Support for class-based AOP in step classes in Spring Please raise a different issue for the proxy behaviour Add Comment JBehave / JBEHAVE-1045 Support for class-based AOP in step classes in Spring When I add @EnableAspectJAutoProxy in my spring setup, with the bundled steps factory, my step beans can't be found. I've done my own steps factory... it assumes the use of a specific type annotation on the step classes, to make it more clear which beans to explore, but that can be removed in a more general case. Here it's how it looks like (WIP): ... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1045) Support for class-based AOP in step classes in Spring
Title: Message Title
Mauro Talevi commented on an issue
Re: Support for class-based AOP in step classes in Spring
Just be aware that you should not rely on any custom bean annotation.
All the beans in the context should be considered that have JBehave-annotated methods. So you should start from the method
@Override
protected ListClass? stepsTypes() {
ListClass? types = new ArrayListClass?();
for (String name : context.getBeanDefinitionNames()) {
Class? type = context.getType(name);
if (isAllowed(type) hasAnnotatedMethods(type)) {
types.add(type);
}
}
return types;
}
Add Comment
JBehave / JBEHAVE-1045
Support for class-based AOP in step classes in Spring
When I add @EnableAspectJAutoProxy in my spring setup, with the bundled steps factory, my step beans can't be found. I've done my own steps factory... it assumes the use of a specific type annotation on the step classes, to make it more clear which beans to explore, but that can be removed in a more general case. Here it's how it looks like (WIP): ...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[jbehave-dev] [jira] (JBEHAVE-1044) Multi-threading in scenarios example tables
Title: Message Title Mauro Talevi commented on an issue Re: Multi-threading in scenarios example tables No, the parametrised scenarios do not support multi-threading either. The executable boundary for concurrent execution is the story. Add Comment JBehave / JBEHAVE-1044 Multi-threading in scenarios example tables We have many stories, and one story has 10-20 scenarios. It cost much time to run all of them by serial. I know JBehave support multi-threaded story execution capability, could you also support multi-threaded in scenario level and different data in example table? This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1043) GivenStories are not working for me in jbehave-web-selenium [3.6-beta-2]
Title: Message Title Mauro Talevi commented on an issue Re: GivenStories are not working for me in jbehave-web-selenium [3.6-beta-2] Can you please provide a self-contained project reproducing the issue? http://jbehave.org/how-to-contribute.html Add Comment JBehave / JBEHAVE-1043 GivenStories are not working for me in jbehave-web-selenium [3.6-beta-2] Hi I am new in Jbehave and trying to setup automation framework using Jbehave[3.9.3] and selenium[2.42.2]. I am using Ivy to execute the test. I could able to do that successfully. GivenStories are not working for me. I am sorry if this is not the right place to ask this question. After trying for couple days and looking into the comments that Give... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1042) Support package scanning for annotated Steps classes
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1042 Support package scanning for annotated Steps classes Change By: Mauro Talevi AddScanningStepsFactoryimplementationtoretrieveandinstantiateStepsclassesbyscanningconfiguredpackagesandfindingclassescontainingannotatedmethods. Itcanusedprogrammaticallyorviathe@UsingStepsannotation. Scanningwillrequireoptionalorg.reflections:reflectionsdependency. Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1037) Story duration timeout occurs for not started story
Title: Message Title Mauro Talevi resolved an issue as Fixed Fixed by JBEHAVE-1041 . JBehave / JBEHAVE-1037 Story duration timeout occurs for not started story Change By: Mauro Talevi Resolution: Fixed Assignee: MauroTalevi Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1041) Allow StoryManager to calculate story durations
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1041 Allow StoryManager to calculate story durations Change By: Mauro Talevi ThestorydurationsascalculatedinthePostStoryStatisticsCollectorarenotreliableinmulti-threadingexecutions.TheStoryManagershouldberesponsiblefortheircalculation. Thedurationshouldbecalculatedfromthestartofthecallabletaskandnotthesubmission. Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1041) Allow StoryManager to calculate story durations
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1041 Allow StoryManager to calculate story durations Change By: Mauro Talevi ThestorydurationsascalculatedinthePostStoryStatisticsCollectorarenotreliableinmulti-threadingexecutions.TheStoryManagershouldberesponsiblefortheircalculation.Theduration (andhencethetimeout) shouldbecalculatedfromthestartofthecallabletaskandnotthesubmission. Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1042) Support package scanning for annotated Steps classes
Title: Message Title Mauro Talevi created an issue JBehave / JBEHAVE-1042 Support package scanning for annotated Steps classes Issue Type: Improvement Assignee: Mauro Talevi Created: 21/Aug/14 4:08 PM Fix Versions: 3.9.4 Priority: Minor Reporter: Mauro Talevi Add ScanningStepsFactory implementation to retrieve and instantiate Steps classes by scanning configured packages and finding classes containing annotated methods. Scanning will require optional org.reflections:reflections dependency. Add Comment This message
[jbehave-dev] [jira] (JBEHAVE-1042) Support package scanning for annotated Steps classes
Title: Message Title Mauro Talevi resolved an issue as Fixed JBehave / JBEHAVE-1042 Support package scanning for annotated Steps classes Change By: Mauro Talevi Resolution: Fixed Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1041) Allow StoryManager to calculate story durations
Title: Message Title Mauro Talevi resolved an issue as Fixed JBehave / JBEHAVE-1041 Allow StoryManager to calculate story durations Change By: Mauro Talevi Resolution: Fixed Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1041) Allow StoryManager to calculate story durations
Title: Message Title Mauro Talevi created an issue JBehave / JBEHAVE-1041 Allow StoryManager to calculate story durations Issue Type: Improvement Assignee: Mauro Talevi Created: 18/Aug/14 3:24 PM Fix Versions: 3.9.4 Priority: Major Reporter: Mauro Talevi The story durations as calculated in the PostStoryStatisticsCollector are not reliable in multi-threading executions. The StoryManager should be responsible for their calculation. Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[jbehave-dev] [jira] (JBEHAVE-1039) Scenarios not allowed by filter are not skipped and cause NPEs
Title: Message Title Mauro Talevi created an issue JBehave / JBEHAVE-1039 Scenarios not allowed by filter are not skipped and cause NPEs Issue Type: Bug Assignee: Mauro Talevi Created: 16/Aug/14 8:38 AM Fix Versions: 4.0 Priority: Major Reporter: Mauro Talevi Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1039) Scenarios not allowed by filter are not skipped and cause NPEs
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1039 Scenarios not allowed by filter are not skipped and cause NPEs Change By: Mauro Talevi Attachment: metatags.zip Onlyoccursin4.xduringtheexecutionofthePerformableStory. Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1039) Scenarios not allowed by filter are not skipped and cause NPEs
Title: Message Title Mauro Talevi resolved an issue as Fixed JBehave / JBEHAVE-1039 Scenarios not allowed by filter are not skipped and cause NPEs Change By: Mauro Talevi Resolution: Fixed Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1037) Story duration timeout occurs for not started story
Title: Message Title Mauro Talevi commented on an issue Re: Story duration timeout occurs for not started story Is the time spent in the @Before methods such that it could account for the timeout? From the execution point of view, a story duration also includes all before and after steps, so if the before steps take a long time the story itself may not start at all. Could you please provide a sample project that reproduces this behaviour? Add Comment JBehave / JBEHAVE-1037 Story duration timeout occurs for not started story Some time (useStoryTimeoutInSecs) after starting my tests web browser is closed with warning [WARNING] Story com/sample/qa/stories/login.story duration of 101 seconds has exceeded timeout of 100 seconds. No one executed story exceed this time. This is even before login.story execution. The clue is that the story contains all @Before and @After method... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit:
[jbehave-dev] [jira] (JBEHAVE-1038) Unable to resolve dependencies using ANT
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1038 Unable to resolve dependencies using ANT Change By: Mauro Talevi Affects Version/s: 4.x Fix Version/s: 3.9.4 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1038) Unable to resolve dependencies using ANT
Title: Message Title Mauro Talevi resolved an issue as Fixed Applied URL changed as suggested, with thanks. JBehave / JBEHAVE-1038 Unable to resolve dependencies using ANT Change By: Mauro Talevi Resolution: Fixed Assignee: MauroTalevi Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1037) Story duration timeout occurs for not started story
Title: Message Title Mauro Talevi commented on an issue Re: Story duration timeout occurs for not started story Does this occur with 3.9.x as well? Add Comment JBehave / JBEHAVE-1037 Story duration timeout occurs for not started story Some time (useStoryTimeoutInSecs) after starting my tests web browser is closed with warning [WARNING] Story com/sample/qa/stories/login.story duration of 101 seconds has exceeded timeout of 100 seconds. No one executed story exceed this time. This is even before login.story execution. The clue is that the story contains all @Before and @After method... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1036) StoryReporterBuilder fails to parse test results if story has GivenStories
Title: Message Title
Mauro Talevi commented on an issue
Re: StoryReporterBuilder fails to parse test results if story has GivenStories
Rather than providing a set of morsels of code and configuration, it'd be much easier if you could provide a simple Maven sample project that reproduced this behaviour.
Add Comment
JBehave / JBEHAVE-1036
StoryReporterBuilder fails to parse test results if story has GivenStories
In case of story with GivenStories JBehave raport is broken. Although few scenarios has been successfully performed - Scenarios and Steps are missing. Duration is improperly set to zero. {code:title=Example of problematic story:|borderStyle=solid} @author Przemyslaw Kwiecien @organization Example Organization Systems Ltd. GivenStorie...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-712) Spaces in path breaks StoryFinder().findPaths()
Title: Message Title Mauro Talevi commented on an issue Re: Spaces in path breaks StoryFinder().findPaths() Can you provide an example or a unit test reproducing the problem? Add Comment JBehave / JBEHAVE-712 Spaces in path breaks StoryFinder().findPaths() Constructions like: ListString storyPaths = new StoryFinder().findPaths(codeLocationFromClass(getClass()), **/*.story, **/*examples.story); or ListString storyPaths = new StoryFinder().findPaths(codeLocationFromPath(somePath), **/*.story, **/*examples.story); doesn't work when there are spaces in a path (which are replaced to %20). An... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1035) @BeforeStory steps not performed before GivenStories
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1035 @BeforeStory steps not performed before GivenStories Change By: Mauro Talevi Affects Version/s: web-3.5.5 Affects Version/s: 4.x Fix Version/s: 4.x Fix Version/s: 4.0 Summary: DelegateWebDriverNotFound:WebDriverhas @BeforeStorysteps not beenfoundforthisthread. performedbeforeGivenStories Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1035) @BeforeStory steps not performed before GivenStories
Title: Message Title Mauro Talevi resolved an issue as Fixed JBehave / JBEHAVE-1035 @BeforeStory steps not performed before GivenStories Change By: Mauro Talevi Resolution: Fixed Assignee: MauroTalevi Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1035) @BeforeStory steps not performed before GivenStories
Title: Message Title
Mauro Talevi commented on an issue
Re: @BeforeStory steps not performed before GivenStories
4.0-beta-9 has been released.
4.0-SNAPSHOT has also been deployed. The deployment is not automatic as yet because we need to find a way of securing the credentials on the CI server.
Add Comment
JBehave / JBEHAVE-1035
@BeforeStory steps not performed before GivenStories
There seems to be a bug in 4.0-beta-8 concerning the usage of GivenStories. If I have a story which uses GivenStories then I get this exception: {noformat} org.jbehave.web.selenium.DelegatingWebDriverProvider$DelegateWebDriverNotFound: WebDriver has not been found for this thread. Please verify you are using the correct WebDriverProvider, with t...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1035) DelegateWebDriverNotFound: WebDriver has not been found for this thread.
Title: Message Title
Mauro Talevi commented on an issue
Re: DelegateWebDriverNotFound: WebDriver has not been found for this thread.
Does it happen only with GivenStories?
Add Comment
JBehave / JBEHAVE-1035
DelegateWebDriverNotFound: WebDriver has not been found for this thread.
There seems to be a bug in 4.0-beta-8 concerning the usage of GivenStories. If I have a story which uses GivenStories then I get this exception: {noformat} org.jbehave.web.selenium.DelegatingWebDriverProvider$DelegateWebDriverNotFound: WebDriver has not been found for this thread. Please verify you are using the correct WebDriverProvider, with t...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1035) DelegateWebDriverNotFound: WebDriver has not been found for this thread.
Title: Message Title
Mauro Talevi commented on an issue
Re: DelegateWebDriverNotFound: WebDriver has not been found for this thread.
Please pull latest 4.x and try out snapshot.
Add Comment
JBehave / JBEHAVE-1035
DelegateWebDriverNotFound: WebDriver has not been found for this thread.
There seems to be a bug in 4.0-beta-8 concerning the usage of GivenStories. If I have a story which uses GivenStories then I get this exception: {noformat} org.jbehave.web.selenium.DelegatingWebDriverProvider$DelegateWebDriverNotFound: WebDriver has not been found for this thread. Please verify you are using the correct WebDriverProvider, with t...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1032) Allow MetaMatcher to be injectable
Title: Message Title Mauro Talevi created an issue JBehave / JBEHAVE-1032 Allow MetaMatcher to be injectable Issue Type: Improvement Assignee: Mauro Talevi Components: Core Created: 12/Jul/14 2:15 AM Fix Versions: 3.9.4 Priority: Major Reporter: Mauro Talevi To support custom implementations and extensibility of the meta matching, the MetaMatcher should be injectable and default to the implementations provided in core if not injected. Add Comment
[jbehave-dev] [jira] (JBEHAVE-1033) Add JiraMetaMatcher
Title: Message Title Mauro Talevi created an issue JBehave / JBEHAVE-1033 Add JiraMetaMatcher Issue Type: New Feature Assignee: Unassigned Components: REST Support Created: 12/Jul/14 2:17 AM Fix Versions: 3.9.4 Priority: Major Reporter: Mauro Talevi A MetaMatcher that looks up a JIRA issue via REST and allows the meta if the issue is open. Add Comment
[jbehave-dev] [jira] (JBEHAVE-961) Customize JBehave HTML report.
Title: Message Title Mauro Talevi commented on an issue Re: Customize JBehave HTML report. Currently, users can provide their own meta properties. We could allow these to also be read from other sources, e.g. env variables. Add Comment JBehave / JBEHAVE-961 Customize JBehave HTML report. Is there any way to customize HTML the way we want in JBehave? As per our project requirement, we want to add more information in HTML report such as date time, browser tested etc. We noticed HTMLoutput method in JBehave. If it is possible with this method can you please provide any good example? This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1028) Add support for Korean locale
Title: Message Title Mauro Talevi commented on an issue Re: Add support for Korean locale I understand that an oriental language flow may different from a Latin-based one, but I struggle to understand what's the use of having a Korean locale with keywords in English. Then it's just as well to use the default locale. I think it would be beneficial to have the keywords translated in Korean, which can be used regardless of the position in the sentence. Then we can try to address the positioning issue separately. Add Comment JBehave / JBEHAVE-1028 Add support for Korean locale While following http://jbehave.org/reference/stable/running-examples.html page, next command failed with following message. mvn -s settings.xml clean install -Pexamples Tests run: 11, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.018 sec FAILURE! - in org.jbehave.core.reporters.StoryReporterBuilderBehaviour shouldBuildWithReporterOfDiff... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from
[jbehave-dev] [jira] (JBEHAVE-1028) Add support for Korean locale
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1028 Add support for Korean locale Change By: Mauro Talevi Summary: runningprofile'examples'failedduetolackofbundlefilewhen AddsupportforKorean locale ko_KR Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
