I think the issue looks not simple as it sounds to be,, all we need is the step number where the application got crashed or any error occurred
I am sure there is an easy way to find it, its just not we used it before ANYONE think of ? --- On Fri, 3/16/12, Deepak Kumar Mahapatro <[email protected]> wrote: From: Deepak Kumar Mahapatro <[email protected]> Subject: Re: Recover scenario - step before trigger To: [email protected] Date: Friday, March 16, 2012, 12:35 PM It not actually called log file. It can be any file to keep track of the step execution. You can maintain any file to keep track of your process. You can keep track of the step execution using Reporter.ReportEvent statement frequently during the test. When the application crashes, following the test result, you can know about the step execution before crash. hope it will help. On Fri, Mar 16, 2012 at 5:34 PM, uma mahesh <[email protected]> wrote: Deepak, Can you please explain it elaborate. what is log file. -- You received this message because you are subscribed to the Google "QTP - HP Quick Test Professional - Automated Software Testing" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MercuryQTP?hl=en -- Deepak Kumar Mahapatro -- You received this message because you are subscribed to the Google "QTP - HP Quick Test Professional - Automated Software Testing" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MercuryQTP?hl=en -- You received this message because you are subscribed to the Google "QTP - HP Quick Test Professional - Automated Software Testing" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MercuryQTP?hl=en
