As Louis correctly says, it's most likely not JBehave that is the
bottleneck in your testing.
Rather it's likely the system under test or the amount of data that
you're processing.
That's not to say that the testing layer can't be improved in
performance, in some cases effort is well spent.
But you need to assess if it's worth it.
"Premature optimatisation is the root of all evil" as Donald Knuth would
say ... :-)
On 08/01/2013 16:48, louis gueye wrote:
Depends on what you're testing...
Provide more context on what you want to achieve and what seems slow
to you.
I don't recall jbehave beeing slow or slowing down my test. Most time
my tests are poorly written in terms of performance.
2013/1/8 Jitendrasbhati <[email protected]
<mailto:[email protected]>>
Hi all,
How can I improve automated test execution speed. I am using
following version:
Jbehave - 3.6.2
Thanks,
Jitendra
--
Cordialement/Regards,
Louis GUEYE
linkedin <http://fr.linkedin.com/in/louisgueye> | blog
<http://deepintojee.wordpress.com/> | twitter
<http://twitter.com/#%21/lgueye>
