Novice Question - Testing Delphi App
Hi I am newbie to TestComplete and currently using it to test our app (written in delphi and operating SQL server datasource). Our app is quite stable and has been used by our customers for years. ...
Forum Discussion
Hi Kevin,
If I've well understood, the last succesfull action "The button was clicked with the left mouse button" allows you to open the window in wich you want select the "KEV_1".
What I suspect is that this window has not the same element of recognition than when you record the test. the test is looking for a window "A" but there is a "B", so test considers as "unexpected".
This may have several origin :
- The test was recorded with the version N of your application and you try to apply to version N+1. But the building process assign an automatic number to some "anonymous" window. I've already noted this in our application (which is also in Delphi)
- The name of the window is dependant of some parameter during the execution, like "my job title window", where job titla was X during record, and is Y during execution.
What you can do is to add a "pause" in your test after opening the window and use the "Object Spy" to look at the Properties of your window, and then to compare to what is recorded in your test.
Christophe
If I've well understood, the last succesfull action "The button was clicked with the left mouse button" allows you to open the window in wich you want select the "KEV_1".
What I suspect is that this window has not the same element of recognition than when you record the test. the test is looking for a window "A" but there is a "B", so test considers as "unexpected".
This may have several origin :
- The test was recorded with the version N of your application and you try to apply to version N+1. But the building process assign an automatic number to some "anonymous" window. I've already noted this in our application (which is also in Delphi)
- The name of the window is dependant of some parameter during the execution, like "my job title window", where job titla was X during record, and is Y during execution.
What you can do is to add a "pause" in your test after opening the window and use the "Object Spy" to look at the Properties of your window, and then to compare to what is recorded in your test.
Christophe
