Is it possible to debug on runtime error?
I was wondering if anyone could give me a definitive answer as to whether or not it SHOULD be possible to debug a script after a runtime error. The easiest way of replicating what I mean is to ...
Forum Discussion
I'm not sure actually. A separate issue I'm trying to resolve is that TC crashes when I try to open a TC log. But even if it did, that would only show you where in the code the error happened after the test run has been stopped wouldn't it?
In a more realistic case of having a runtime error in our scripts, we would need to start digging into the objects/variables at runtime to figure out what ultimately caused the error to occur.
Having come from a QTP background, there is a "debug" button on runtime error popups that allows you to debug the error, and from there you can fully debug the error by viewing all of the objects/variables invovled. Then, we can make necessary code changes after the run since we were able to nail down the cause.
That's specifically the type of debugging scenario I'm curious if it should be possible in TC.
In a more realistic case of having a runtime error in our scripts, we would need to start digging into the objects/variables at runtime to figure out what ultimately caused the error to occur.
Having come from a QTP background, there is a "debug" button on runtime error popups that allows you to debug the error, and from there you can fully debug the error by viewing all of the objects/variables invovled. Then, we can make necessary code changes after the run since we were able to nail down the cause.
That's specifically the type of debugging scenario I'm curious if it should be possible in TC.