What is a testcase for you? How many steps classes do you have?
You can add a debug logger level via the JBehave Preferences to see where the bottleneck is. BTW, Have you tried increasing the memory? > On 1 Sep 2014, at 17:49, "Anders" <codeh...@aek.se> wrote: > > The problem is that Eclipse becomes very slow and often hangs with a greyed > out unresponsive GUI after that a story file or a step implementation file > (Java file with Given/When/Then annotations) is edited. > It is enough to type a few letters, no save required, for the > unresponsiveness to start. > > We are using 32 bit Windows 7 for all developer work. > (yes, it is just ridiculous that we are not allowed to use a 64 bit developer > environment, so this is what we have to work with) > > Attached is a simple project that demonstrates the problem. > Load this project up using Eclipse with the latest JBehave plugin, run the > story generator, and then try to edit any story file or step implementation > class, and enjoy the lag. > > Simply run the class GenerateStories to regenerate the stories and step > implementation files. > After this, refresh the project and it now contains 100 generated story > files, each containing 10 scenarios with three steps each, and 100 step > implementation classes / java files. > > The number of stories, scenarios and step implementation classes to be > generated can be configured by changing the values of the constants below: > > public class GenerateStories { > > private final static String OUTPUT_PATH = > "src/main/java/jbehave/stress"; > private final static String STORIES_OUTPUT_PATH = OUTPUT_PATH + > "/usecases"; > private final static String STEPS_OUTPUT_PATH = OUTPUT_PATH + > "/stepimpl"; > > private final static int NUMBER_OF_USECASES = 100; > private final static int NUMBER_OF_STORIES_PER_USECASE = 10; > private final static int NUMBER_OF_SCENARIOS_PER_STORY = 10; > private final static int NUMBER_OF_STEP_IMPLS_PER_JAVAFILE = 100; > // must be same or higher than NUMBER_OF_USECASES for all steps to resolve > > . . . > > > The current situation in our project is unbearable due to this. > We have 1900 test cases running each night, and continuously have to keep the > tests updated and add new tests each and every day. > > Maybe if someone can do some profiling on the plugin, and publishing the > results would help the community to overcome this. > Please help. > > /Anders > <JbehaveStress.zip> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email