DevXpress dateedit calendar
Hi people. I'm quite new to TestComplete, I'm still going through TestComplete's on-demand video trainings and I've hit my first snag. One of many more to come, probably. I'm having problems tes...
Forum Discussion
The two things I would suggest you look into first ....
1. Are the controls being recognised correctly if object if you object spy them? ie. They has all the relevant property data, fields and methods present? It looks like the actual calendar is working OK. (It clicks the cell based on value) The error is on the DateEdit field? I'm guessing the calendar populates the value you select into that field? I'd suspect it's that that's the problem here ...
2. The "hint" before your error line suggests you have object recognition problems (with the edit field, not the calendar itself). As your date edit field is not being populated, it could be that whatever properties you used to map it are not staying consistent at run rime.
Finally, as this is a date field, I reckon you'll have more work ahead here. Have you already parameterised it? As obviously, dates in December won't work in January. Record and playback, without converting at least parts of it to parameters, seldom works for calendars.
Hi, Colin. Tnx for the reply.
Colin_McCrae wrote:The two things I would suggest you look into first ....
1. Are the controls being recognised correctly if object if you object spy them? ie. They has all the relevant property data, fields and methods present? It looks like the actual calendar is working OK. (It clicks the cell based on value) The error is on the DateEdit field? I'm guessing the calendar populates the value you select into that field? I'd suspect it's that that's the problem here ...
I believe TC recognizes everything in order. Once you manually click the drop down menu and pick a date, that date will populate the field you originally clicked. Like this:
My problem is that TC cannot reproduce that field population. It doesn't get that there is a calendar there once you click the little arrow on the right.
2. The "hint" before your error line suggests you have object recognition problems (with the edit field, not the calendar itself). As your date edit field is not being populated, it could be that whatever properties you used to map it are not staying consistent at run rime.
I forgot to include the hint text:
Failed to find the exact match for the test object:
NameMapping.Sys.Client.PropertiesForm.layoutControlProperties.tabControlP.tabPageDocAttr.layoutControlDocAttr.gridControlAttr.DateEdit
Hint: A similar object has been found – see the Picture tab. Consider updating the identification properties to use the similar object:
Property Mapping Value Found Action
| ✓ | ClrFullClassName | DevExpress.XtraEditors.DateEdit | DevExpress.XtraEditors.DateEdit | |
| ⓧ | WndCaption | 2018-05-18 | Update |
View identification properties in the Name Mapping editor
I'm not sure what this August 18th is, though...
Finally, as this is a date field, I reckon you'll have more work ahead here. Have you already parameterised it? As obviously, dates in December won't work in January. Record and playback, without converting at least parts of it to parameters, seldom works for calendars.
Parametrisation hasn't been mentioned in the training video so far. I'm not sure what you mean by this so I'm afraid I don't know what to answer to this question...
There is your problem ...
Hint: A similar object has been found – see the Picture tab. Consider updating the identification properties to use the similar object:
Property Mapping Value Found Action
✓ ClrFullClassName DevExpress.XtraEditors.DateEdit DevExpress.XtraEditors.DateEdit ⓧ WndCaption 2018-05-18 Update It is the Date Edit field.
That second line is why it isn't finding it. I'm guessing you just kept whatever properties it used to capture the object when you recorded this? Well, one of the properties it used looks like a date. Albeit a date in 2018. You probably want to get rid of that as an identification property. The classname on it's own should be sufficient. Presuming you only ever have one on the screen at any given time.
This is something you'll discover. The properties it uses automatically are not always reliable going forward!
