TypeError : textBox.Click is not a function
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
TypeError : textBox.Click is not a function
nameField = dynamicDataDisplayControl.IDataDisplayField0;
textBox = nameField.firstName;
textBox.Click();
textBox.SetText("Abel1");
textBox = nameField.lastName;
textBox.Click(); /// Got Error while executing the script at this point
textBox.SetText("Felix1");
- Labels:
-
Desktop Testing
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you move the last name section above the first name section, does it still fail?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It doesn't work. Actually the generated script was textbox.Click(14, 6) and textbox.Click(20, 9). I have removed the numbers and rerun the script. It did not work.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well no, it wouldn't work that way because now there's nowhere for the Click to happen. You have to have coordinates or an object name.
If you use Object Spy on the last name field, what does it show you?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
WinFormsObject("EditVictimWizardDlg").WinFormsObject("propertyPagePanel").WinFormsObject("pagePanel").WinFormsObject("DynamicDataDisplayWizardPage").WinFormsObject("VictimMainView").WinFormsObject("splitContainer1").WinFormsObject("SplitterPanel", "").WinFormsObject("centerPanel").WinFormsObject("IDataDisplayField0").WinFormsObject("lastName")
If the Script is generated with random click/coordinates, can we use the same Coordinates every time with the new build as well.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Best practice is to use the object name because generally that doesn't change. The coordinates are much more fragile and can break the test more frequently.
