How can I assert if a value is equal to another

[clausbraatz]

How can I assert that a value is equals to another?. What I am tryin to do is assert if a value is true, or maybe assert if a string is equals to another, but not using UI object properties. Is there any checkpoint or something like that to work with own variables?

[Marsha_R]

@tristaanogre gave you the questions to ask in his last reply.  Show that to the developer.

[mcp111]

His reply only said ask more questions about the object. I'm not clear what questions to ask. Can you please clarify exactly what questions would help you to arrive at a solution?

---

@Marsha_R wrote:

@tristaanogre gave you the questions to ask in his last reply.  Show that to the developer.

---

[Marsha_R]

@tristaanogre said this:   "And... if all else fails... contact your developer and ask "Hey, where does that tool-tip reside?  I want to be able to validate it in the automation and I'm having a hard time finding it in the component objects."

Ask your developer that question.  You can also show this whole thread as an explanation of what you are trying to do.  Your developer can help you with your software and once you have that answer we can help you with TestComplete.  

[mcp111]

That's what I'm not clear about.

What exactly do you mean by "Where does that tooltip reside"?

What kind of answer are you looking for?

---

@Marsha_R wrote:

@tristaanogre said this:   "And... if all else fails... contact your developer and ask "Hey, where does that tool-tip reside?  I want to be able to validate it in the automation and I'm having a hard time finding it in the component objects."

Ask your developer that question.  You can also show this whole thread as an explanation of what you are trying to do.  Your developer can help you with your software and once you have that answer we can help you with TestComplete.  

---

[Marsha_R]

The answer to that will be the location of the text that we are trying to help you compare.  I'm not clear why you can't just go show @tristaanogre 's comment to the developer.  

[mcp111]

The location of the text is the tooltip for the red exclamation mark icon which is named as ErrorWindow. That was seen in the properties I had posted earlier.

What I don't understand is why is there no wText property for that tooltip which will show the text.

This is a client application that I am testing and I don't have access to the source code.

I thought testcomplete can do everything with just an executable.

---

@Marsha_R wrote:

The answer to that will be the location of the text that we are trying to help you compare.  I'm not clear why you can't just go show @tristaanogre 's comment to the developer.  

---

[Marsha_R]

Well, okay, but it would have saved a lot of time if you had just said you can't talk to the developers, right?

TestComplete can work with an .exe because its actions on the screen mimic a user.  However, when you start wanting to assert or compare values and your tests are not coming out as expected, then that's beyond user experience and now you have to tell TestComplete what to do.

Why there isn't a wText property where you expect one, I don't know.  You said it was in your documentation but perhaps that is wrong.  If it's not automatic to add one in whatever code this is, then it's possible that the developer didn't do it.  I test all sorts of web pages where there's no Id or Name set up so I have to find another way around to identify the object, or in my case I can ask the developer to add a better identifier.    

When you said earlier that you had been through all the Object Spy properties, does that include digging down all the levels using the buttons on the right with ...  ?  See my attached example.

[mcp111]

Actually I could probably talk to the developer if it is really needed but I must know exactly what question to ask.

I dug deeper into the properties as you suggested in your image but couldn't find tooltip text anywhere.

Even the wText shows as blank.

---

@Marsha_R wrote:

Well, okay, but it would have saved a lot of time if you had just said you can't talk to the developers, right?

TestComplete can work with an .exe because its actions on the screen mimic a user.  However, when you start wanting to assert or compare values and your tests are not coming out as expected, then that's beyond user experience and now you have to tell TestComplete what to do.

Why there isn't a wText property where you expect one, I don't know.  You said it was in your documentation but perhaps that is wrong.  If it's not automatic to add one in whatever code this is, then it's possible that the developer didn't do it.  I test all sorts of web pages where there's no Id or Name set up so I have to find another way around to identify the object, or in my case I can ask the developer to add a better identifier.    

When you said earlier that you had been through all the Object Spy properties, does that include digging down all the levels using the buttons on the right with ...  ?  See my attached example.

---

[Marsha_R]

Once again, exactly what to ask is what @tristaanogre posted before

@tristaanogre said this:   "And... if all else fails... contact your developer and ask "Hey, where does that tool-tip reside?  I want to be able to validate it in the automation and I'm having a hard time finding it in the component objects."

[tristaanogre]

Note: wText is a property that TestComplete adds to certain object classes.  So, there will not always BE a wText property.  This means, rather than looking for that property, you should be looking for the text and, from that, determine which property to use.  This is what you need to go to the developer with.   Ask them:

1) What object in the application contains the tooltip text?

2) What triggers the instantiation of that object?

3) What property on the object contains the tooltip text?

4) When is that property populated with the text?

etc... 

These are just a few questions that I would ask my developer... most of the time, I'd pull up a shared screen, show him/her what I'm trying to do, guide them through the basics of how TestComplete views objects, and then ask them to help me find the text.... this usually takes, probably, about an hour as we spend time, collaboratively, investigating the application under test.