Forum Discussion
Andy_Omelyanenk
10 years agoNew Contributor
Ok, so far I've found out that by disabling Log.Enabled (Log.Enabled := false;)
I effectively disable error logging at all - that is no error will be reported and thus my test will not fail because of that 1 failed UI interaction (I can add some verifications points and fail the test with them).
But is that it? I mean common, even QTP does better than that with its mediocre VBscript capabilities - but QTP gives me more control over error handling even though QTP has no Try/Catch/Finally constructs yet at least QTP lets me obtain the last error that occurred and clear it if necessary rather than fail the whole test.
Why then Test Complete which seems way more advanced than QTP doesn't do it?
I effectively disable error logging at all - that is no error will be reported and thus my test will not fail because of that 1 failed UI interaction (I can add some verifications points and fail the test with them).
But is that it? I mean common, even QTP does better than that with its mediocre VBscript capabilities - but QTP gives me more control over error handling even though QTP has no Try/Catch/Finally constructs yet at least QTP lets me obtain the last error that occurred and clear it if necessary rather than fail the whole test.
Why then Test Complete which seems way more advanced than QTP doesn't do it?
Related Content
- 3 years agoStephenOrion
Recent Discussions
- 3 days agoMW_Didata