Hi, I have also observed memory related issues while running testsuites having large number of steps. I resolved the issue by increasing the java heap size. There may be other related compilation tasks, but bottom line is the Java Heap Size is too small. To increase it, you need to add $ANT_OPTS to your environment.
For e.g:- ANT_OPTS=”-Xmx1024m -Xms512m” Thanks & Regards, Hitesh Gupta On Tue, Mar 16, 2010 at 6:17 PM, Michael Zwick <[email protected]>wrote: > Hi, > > > > I know, memory has been an issue on the list a couple of times. But I could > not find answers to my questions. > > > > My case: > > When running our WebTest Suite (with webtest R_1758) during the nightly > builds the resident memory consumption goes up to almost 2 GB. That’s > clearly too much and a knock out for Canoo WebTest and plans expanding the > suite in the future in my company. > > > > Some details: > > There are 800 steps in total. The tests are organized as recommended like > > |-- allTests.xml > > | |-- Verify_blabla.xml > > | |-- Verify_blublu.xml > > | |-- ….. (about 15 additonal Verify_....xml files) > > | |-----------------| about 10 WebTest tasks in each of the Verify_...xml > files > > | |-----------------|--------| every WebTest task with 5 to 25 steps > > > > At the end I get a single test report for the suite. > > > > I monitored the memory consumption with JConsole. What I see is a steady > increase over time. > > > > In the manual it says: “When your test suite grows beyond some thousand > steps consider using more than one file for collecting the reports.” I’m not > at the 1000 steps limit yet, but still, what does that mean? Is the > recommendation to split up the test suite into various separate ANT > projects? > > > > How do other people cope with this sort of thing? > > Any other people having memory issues? > > Anyone else running a large test suite? > > > > I’d be curious to find out more about the experiences of others with large > tests suites and their memory consumptions. > > > > Thanks, > > Michael > > >
