On Tue, Sep 15, 2009 at 3:13 PM, John LaBanca <[email protected]> wrote:
> You wouldn't necessarily want to use it if the tests are going to run > locally in hosted mode because the CPU is usually pegged anyway, but even > then it probably wouldn't hurt because of the Timers in some UISuite tests. > > You would want to use it in the following cases: > > - If your remote test machines are scarce (ex. a shared test > infrastructure), you can use "-precompile all" to compile all modules > before > sending any tests to the test machines. This would reduce the amount of > time needed on the test machines. This change also allows remote systems > to > run out of sync with each other, so one can complete before another starts. > - If your remote machines are slow or you have Timers in your tests, > you can use "-precompile parallel" to compile future modules while the > current one executes. This is useful for remoteweb and selenium tests > because the host usually sits idle waiting for the client machines to > finish > the tests. > > All remote tests benefit from the -userAgents option because we current > compile for all user agents when running remote tests, even if we connect to > only one system. > Gotcha. I guess we'll need to update doc? > @FYI - > jgw only reviewed a small incremental change. fabbott and I did most of > the review. > Hehe, I figured. :) --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
