Forum Discussion

Draconai's avatar
Draconai
New Contributor
12 years ago

Step Testing behaving differently than Run Testing.

I've encountered a situation where a Test executes an app differently if I have breakpoints in my Test Script than it does if I just let it run.



I have a ButtonClick event called for and it activates another window. which I search in the next bit of code.



The breakpoints function normally, as does the app.

The ButtonCiick acts normally and produces the expected window.



When I run the same Test Script without breaks, even with Delay()s in it, the ButtonClick appears to take place but the result window never appears.



No other changes - just the break points.



Anyone else run into this?



1 Reply

Sort By
  • dganov's avatar
    dganov
    Staff
    12 years ago
    I think that when test execution pauses at breakpoint your application window looses focus and when you continue test execution TestComplete performs some additional actions to activate your application window (and maybe something else) before clicking on the button. Try to analyze what may prevent the click without breaks. If you made your test by hand then try to record the problematic action and compare the recorded test to yours.