Hello,
When scheduling a test list the 3rd step is to select notification settings. 3 options are available:
1. When execution is complete or on unexpected failure.
2. Only on execution failure (hang/timeout)
3. Only on test failure.
I do not have a clear understanding of the differences nor are they documented. Can you please explain?
Thanks in Advance,
Nick
When scheduling a test list the 3rd step is to select notification settings. 3 options are available:
1. When execution is complete or on unexpected failure.
2. Only on execution failure (hang/timeout)
3. Only on test failure.
I do not have a clear understanding of the differences nor are they documented. Can you please explain?
Thanks in Advance,
Nick
1 Answer, 1 is accepted
0
Hi,
1) Basically this will notify you no matter what happens. If the test passes successfully you probably won't need to even look at the log but you will still get an email. If the test fails for any reason at all (if any step shows up as Failed) you will also receive an email.
2) This will send out an e-mail only if a "normal" error is encountered. By normal error I mean an error that's related to the HTML/Silverlight/WPF app that's under testing (missing controls, wrong text values etc.)
3) This will send an e-mail only if there was test failure not related to the actual app that's under testing. e.g. the Execution server on the intended machine might be switched off.
Regards,
Stoich
the Telerik team
1) Basically this will notify you no matter what happens. If the test passes successfully you probably won't need to even look at the log but you will still get an email. If the test fails for any reason at all (if any step shows up as Failed) you will also receive an email.
2) This will send out an e-mail only if a "normal" error is encountered. By normal error I mean an error that's related to the HTML/Silverlight/WPF app that's under testing (missing controls, wrong text values etc.)
3) This will send an e-mail only if there was test failure not related to the actual app that's under testing. e.g. the Execution server on the intended machine might be switched off.
Regards,
Stoich
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items