Re: [jbehave-dev] Hello lists

2008-10-23 Thread Dan North
Hi lists.

Apologies if anyone has been getting mails bounced by the dev list. There
was a problem with the codehaus mail servers which is fixed now. Please try
again if you had a message returned.

Also "Joe Walnes" is a well-known spambot based on the original Eliza system
that takes keywords like "JBehave" and "squirrel" and crafts them into
seemingly human sentences. Apologies that "the Gnome", as this particular
variant is known, managed to infiltrate the JBehave dev list.

Thanks,
Dan

2008/10/19 Joe Walnes <[EMAIL PROTECTED]>

> On Thu, Oct 16, 2008 at 2:21 PM, Dan North <[EMAIL PROTECTED]> wrote:
> > It would be great if you could send a short message introducing yourself
> to
> > the list (long-time lurkers, new faces, dev team, spambots)
>
> I'm Joe. One night whilst drunk, I tripped on a squirrel and my face
> landed on the keyboard of a console that was already logged in to the
> codehaus web interface. 9 months later, I found myself subscribed to
> this list.
>
> > and especially to let us know how you are finding JBehave 2 and where
> > you would like it to go next.
>
> What's JBehave?
>
> -
> To unsubscribe from this list, please visit:
>
>http://xircles.codehaus.org/manage_email
>
>
>


[jbehave-dev] [jira] Commented: (JBEHAVE-141) StepsConfiguration - can it have a setMonitor(..) method please

2008-10-23 Thread Mauro Talevi (JIRA)

[ 
http://jira.codehaus.org/browse/JBEHAVE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151745#action_151745
 ] 

Mauro Talevi commented on JBEHAVE-141:
--

Hi Paul - can you attach the patch that displays the use case?



> StepsConfiguration - can it have a setMonitor(..) method please
> ---
>
> Key: JBEHAVE-141
> URL: http://jira.codehaus.org/browse/JBEHAVE-141
> Project: JBehave
>  Issue Type: Wish
>  Components: Core
>Reporter: Paul Hammant
>
> See also JBEHAVE-140
> When using Selenium it is customary to use setUp (or modern equiv) to acquire 
> a Selenium instance.
> Yet JBehave's Scenario sub-classes and Steps sub-classes are all about 
> setting everything in super(..) calls.  You can't in Java use member 
> variables before super() invocations have all finished.   
> I have patched a version of JBehave and can confirm that this works. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[jbehave-dev] [jira] Created: (JBEHAVE-142) RunnableScenario.addSteps(CandidateSteps) -> method needed

2008-10-23 Thread Paul Hammant (JIRA)
RunnableScenario.addSteps(CandidateSteps) -> method needed
--

 Key: JBEHAVE-142
 URL: http://jira.codehaus.org/browse/JBEHAVE-142
 Project: JBehave
  Issue Type: Wish
Affects Versions: 2.1
Reporter: Paul Hammant


Living in the constructor for adding of Steps subclasses is proving to be 
tiresome.

Can RunnableScenario gain a new method addSteps(CandidateSteps) please ?

It will allow for greater control for the users of JBehave.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[jbehave-dev] [jira] Created: (JBEHAVE-141) StepsConfiguration - can it have a setMonitor(..) method please

2008-10-23 Thread Paul Hammant (JIRA)
StepsConfiguration - can it have a setMonitor(..) method please
---

 Key: JBEHAVE-141
 URL: http://jira.codehaus.org/browse/JBEHAVE-141
 Project: JBehave
  Issue Type: Wish
  Components: Core
Reporter: Paul Hammant


See also JBEHAVE-140

When using Selenium it is customary to use setUp (or modern equiv) to acquire a 
Selenium instance.

Yet JBehave's Scenario sub-classes and Steps sub-classes are all about setting 
everything in super(..) calls.  You can't in Java use member variables before 
super() invocations have all finished.   

I have patched a version of JBehave and can confirm that this works. 




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[jbehave-dev] [jira] Created: (JBEHAVE-140) new StepMonitor method - executingStep(..)

2008-10-23 Thread Paul Hammant (JIRA)
new StepMonitor method - executingStep(..)
--

 Key: JBEHAVE-140
 URL: http://jira.codehaus.org/browse/JBEHAVE-140
 Project: JBehave
  Issue Type: Wish
  Components: Core
Affects Versions: 2.1
Reporter: Paul Hammant


I would suggest at least the parameters include step narrative.

Why? Selenium has a setContext(String) method [ I added it four years ago ].  
It's nice to display what is currently going on in the tests, in case someone 
is watching.

I'd like the Selenium control frame to say "Given I am not logged in" etc.

I have no easy way of doing this presently.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email