Hi Mike,

we would surely welcome an alternative parser.     The architecture
allows for alternative impls and as long as there is no tie-in with an IDE
to can go in core.   For anything that requires a specific IDE, we'd
create a separate module.

Could you please create a new JIRA issue with a patch providing your
parser impl?

As for making the debugging more user-friendly, JBehave 3 has make some
progress on this front.
E.g. it now makes steps pending if examples tables headers do not match
the paramenter names.

JBehave 3 latest beta is stable and being used in several projects.   We
are looking to cut a RC quite soon.

Cheers

On 06/07/2010 17:02, [email protected] wrote:
> Hi,
>
> We've recently started using JBehave for our testing. It's helping us to
> define better system tests which can be added to an automated regression
> suite. However, there are a few weaknesses.
>
> One limitation that is really slowing down the writing of tests based on
> JBehave is a difficulty in debugging tests when they fail. For example, if
> the number of parameters in an examples table is incorrect then the
> standard JBehave error messaging is a little obscure. Similarly if a Given
> clause is missing, then it is not immediately obvious why the test has
> failed.
>
> Is this something that the team are looking to address?
>
> To help address this, we've actually been looking at the JBehave source
> code and have started work on implementing a new parser that would
> facilitate improvements in the error reporting. It is based on Eclipse
> JFace and now allows us to track line numbers in error reporting and thus
> makes it much quicker to identify if a test has failed due to an error in
> the JBehave script. An added advantage of using this parser is that it can
> be re-used for syntax highlighting in an Eclipse editor and the parser is
> also very fast compared to the current regex-based parser - as an example,
> one of our longest running tests was 25s for the previous parser, and now
> its just 0.5s.
>
> Would this new parser be of interest for a future version of JBehave? If
> so, how can we arrange to submit the code?
>
> Thanks,
>       Mike
>
>
> The book, the web, the phone
> Whatever you want, just Yell
>
>
> [Information] -- PostMaster:
> This transmission is intended solely for the addressee(s) and may be 
> confidential. If you are not the named addressee, or if the message has been 
> addressed to you in error, you must not read, disclose, reproduce, distribute 
> or use this transmission. 
>
> Delivery of this message to any person other than the named addressee is not 
> intended in any way to waive confidentiality.  If you have received this 
> transmission in error please contact the sender or delete the message. 
>
> Thank you.
>
> Yell Limited, Queens Walk, Oxford Road, Reading, Berkshire, RG1 7PT. 
> Registered in England and Wales, registered number 4205228.
>
> Yellow Pages Sales Limited, Queens Walk, Oxford Road, Reading, Berkshire, RG1 
> 7PT. Registered in England and Wales, registered number 1403041.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>   


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to