| || |
Anti Virus and other Scheduled Jobs during runs
How do you handle Scheduled Jobs which should run on your servers during runs? On one hand, they add to the "noise", and some R&D personnel would yell that they interfere with the tests (and therefore, the tests are not reliable, of course [img]images/icons/wink.gif[/img] ). On the other hand, these jobs would also run on production servers, so you can't just ignore them.
Another related issue is "unknown jobs", the "I didn't even know it was running" kind of jobs, which tend to show you as a little non-proffessional. How do you detect these, or at least, where do you look for them?
Re: Anti Virus and other Scheduled Jobs during runs
Trying to schedule them when nothing is running (like Sunday 2am). I believe if you want to test how it will work with specific jobs running - make a separate test explicitly starting these jobs...
For "unknown jobs" - monitor your servers and always look for something unusual / any activity between tests.