You were recording so TC gets all its values from you.
Click doesn't take a value parameter. It is clicking the object named in Item. Description is just a report of what happened.
Yes, you are correct. Clicking only on coordinates doesn't make for a portable test. This is why recording is just the beginning of test development. You'll find places where you need to adject the test manually in order to make it robust for your application and your system.
TC is very good at generic tests and getting you started. It is not possible for the TC software to know all apps and all systems, so it will get you very close and then you have to make changes in the parts where you are the expert.
For testing across Citrix, you are going to need to put a copy of TC on the Citrix side. Otherwise you are stuck with what tristaanogre explained above.
OK, but it still clicks at different locations in the same window depending on which step it is. What accounts for the differences?
bistritapcv wrote:
OK, but it still clicks at different locations in the same window depending on which step it is. What accounts for the differences?
If you double click on the recorded line and look at the parameters on the Click action, you will see an X and a Y numeric. These are pixel locations that determine where the click occurs on the window. It is the ONLY way, in your current set up, that the test is working. Change the resolution on the system, resize the window, and the test will fail.
bistritapcv wrote:
OK, but it still clicks at different locations in the same window depending on which step it is. What accounts for the differences?
The object is being clicked and there is no guarantee of the coordinates. Description is reporting what happened. When you manually click a button, I'm sure you don't click it in exactly the same place every time and there's nothing wrong with that.
As tristaanogre have both said, you need to get away from the coordinates.
I understand that, but the button takes up only a small portion of the window. If the window goes from like (0,0) to (100,100) but the button may only be (30,30) - (50,50), so if you just have it click the window, it may miss the button.
Refer up thread... this is the danger that you run operating against an application that is being served up by Citrix. TestComplete has no visibility for the buttons, all it can do is work with co-ordinates, unless you want to use Text Recognition or OCR.
https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/ocr/index.html
