Hi if this would fix it, than go for it.
and if you only hve this test suite, it is ok, but if you are planning on using 20 test suites, and you have to divide each into 4 this will result into 80 CCNet projects. (not so good for an overview) another option is to split it up in different task sections inside 1 ccnet project --> suppose you do now <tasks><exex>...</exec></tasks> and this takes 2 hours, you can try the following <tasks> <exec> part 1 </exec> <exec> part 2 </exec> <exec> part 3 </exec> ... <tasks> so the exe's you call do not have to run 2 hours, but shorter periods maybe this fixes the IE problem But is IE the cause of the problem, or is it also fixed if you increase the timeout of the involved tasks. with kind regards Ruben Willems On Mon, Feb 23, 2009 at 12:36 PM, sam <[email protected]> wrote: > > HI Ruben > > Yes I am using it as a service. Handling popups well. Small projects > work well. But in this project its time execution time is 2 hours. > Should I cut of the project into small modules and then run. What do u > say. > > Kind Regards > >
