Is there recommended TestExecute lify cycle time?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there recommended TestExecute lify cycle time?
Is there recommended time for TestExecute life cycle?
If I use the TE process without closing and restarting, is there any problem occurs such as lose in speed or memory leak?
I have test cases consistently, so I won't kill the process(also the computer which process is running).
How long can I keep the process on?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I usually run TestExecute as a command line in a windows task scheduler, including the /exit command line switch.
I don't know if there is a "recommended" cycle... there's nothing documented. But I also don't see any benefit to keeping the TestExecute service open in windows unless you specifically need it.
Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff
----
Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.
Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can keep the process ON for the indefinite time period (that might affect the system performance a bit), but I don't see any benefits of doing so. Why specifically you need to do this?
