Unfortunately, I can't run all of the tests at once, even after a fresh page load. The memory usage in Chrome starts at about 70MB and grows to nearly 1GB before the page dies. There are only a handful of failures, the majority of which are unexpected Ext globals. No tests are throwing exceptions.
So I'm looking for advice/guidance/feedback regarding how to deal with this. Was Siesta designed to handle such a large # of tests? Are their any options I'm missing to help Siesta free up the memory? What am I doing wrong or what I can do better?
I'm not dismissing that the components in my "app" may be leaking memory. However, if I only run the tests against the models, then memory still grows to almost 500MB.
I am running Chrome 17. Siesta is running Ext 4.0.7 and my app is running Ext 4.1 beta 2.
My harness config:
Harness.configure({
autoCheckGlobals: true,
expectedGlobals: [...],
forceDOMVisible: Ext.isIE,
needDone: true,
preload: [...],
speedRun: true,
testClass: Portal.TestClass,
title: 'Portal Test Suite',
transparentEx: true, //When true the harness will NOT try to catch any exception.
viewDOM: true
});