Yes, it is subjective. "Background" is not perfect, I agree. Another topic: Lifecycle refers to scenarios. But I think there are cases where a JBehave user needs the same for stories. I compare it to JUnit where there is @Before and @After which is executed for every test in a class. A JUnit class is comparable to a story in a way. What is missing then is something like @BeforeClass and @AfterClass. In a story it could be done with GivenStories to support something like @BeforeClass from JUnit. But it seems there is no thing for @AfterClass in a story. Cleanups could be done for all scenarios of a story in such a part. A solution might be to put it into the last scenario of a story maybe.
On Mon, Apr 28, 2014 at 10:56 PM, Mauro Talevi <[email protected]>wrote: > It's rather debatable whether one sounds more natural or technical than > the other. Also, background tends to suggest concurrency - which is not > the case. > > In any case, it's all subjective. If you prefer, you can configure your > own "custom" company locale (akin to a new language) with the name you > choose. The Eclipse plugin will pick up the locale you've configured in > your Configuration. > > Or you can use the Gherkin syntax directly. > > > On 28/04/2014 12:31, Hans Schwäbli wrote: > >> I have a little suggestion concerning "lifecycle" steps. >> This is a cool feature. But the name "lifecycle" sounds quite technical >> and can intimidate testers and business analysts, unlike the other elements >> of a story. >> In Cucumber they call it "background" which does not sound so technical. >> It is not a big issue for me, but I think a "natural" name like >> "background" would be more appropriate. Of course I could change the >> keyword names locally (for the Eclipse plugin it would be more tricky), but >> just as a feedback. >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
