This question is locked. New answers and comments are not allowed.
On the Web application we are automating, we have one page that has four Tables on it. When we record, we record the Tables Menu to add, delete; move; etc. to each table - this all seems to record correctly.
During Playback it performs all the tests (adding, deleting, moving, etc.) on just the first table (all tests from all four tables). The same is happening with Verification.
Looking at the recording WebUI Test Stuido seems to have called all the four tables the same ID.
Please could you provide a fix or work-around to this.
During Playback it performs all the tests (adding, deleting, moving, etc.) on just the first table (all tests from all four tables). The same is happening with Verification.
Looking at the recording WebUI Test Stuido seems to have called all the four tables the same ID.
Please could you provide a fix or work-around to this.
1 Answer, 1 is accepted
0
Hi Mark,
You can start by studying the HTML code generated by your web server and sent to the browser window. If all 4 tables are given the same ID by the web server, then that's what we're going to record against. You may need to modify your code on the server in order to give each table a unique ID.
Another option you can try is to modify the Identification Logic of WebUI Test Studio. Open up the User Settings, go to the Identification Logic tab, then modify it such that it works properly for your web page. This may take some trial and error as this is a very advanced feature.
During recording do you see different elements displayed in Elements Explorer for each of the 4 tables? If so you can try manually modifying the FindParam properties of these elements so that they target the correct element. This approach requires a good understanding of what is truly unique for each table so you can properly modify the FindParam properties. To do this click on the element you want to examine/modify. Look in the Properties window and expand the FindParam node. The properties in here are what WebUI Test Studio uses to locate the element on the web page before trying to interact with it.
We'd also like to study this problem further. To assist us we need a copy of the HTML source code that is exhibiting this behavior during recording. Open an IE browser window and navigate to the page in question. Right click on the page and select View Source. Save the source into a file and send us that file please. You'll need to open a ticket to attach the file.
All the best,
Cody
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
You can start by studying the HTML code generated by your web server and sent to the browser window. If all 4 tables are given the same ID by the web server, then that's what we're going to record against. You may need to modify your code on the server in order to give each table a unique ID.
Another option you can try is to modify the Identification Logic of WebUI Test Studio. Open up the User Settings, go to the Identification Logic tab, then modify it such that it works properly for your web page. This may take some trial and error as this is a very advanced feature.
During recording do you see different elements displayed in Elements Explorer for each of the 4 tables? If so you can try manually modifying the FindParam properties of these elements so that they target the correct element. This approach requires a good understanding of what is truly unique for each table so you can properly modify the FindParam properties. To do this click on the element you want to examine/modify. Look in the Properties window and expand the FindParam node. The properties in here are what WebUI Test Studio uses to locate the element on the web page before trying to interact with it.
We'd also like to study this problem further. To assist us we need a copy of the HTML source code that is exhibiting this behavior during recording. Open an IE browser window and navigate to the page in question. Right click on the page and select View Source. Save the source into a file and send us that file please. You'll need to open a ticket to attach the file.
All the best,
Cody
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.