Sign in to follow this  
Followers 0
mmahima

IE Application(Javascript controls)

4 posts in this topic

We are testing the web application using autoit tool.

I need to click on the few controls designed in the Javascript.

Example:

The node in the tree view control

Images in the javascript.

Is there any method to click on this objects using the autoit

Share this post


Link to post
Share on other sites



You will need to get the control's IDs. I've messed with doing this, but I found it difficult to do. One thing that will help is using FireFox and using a addin called Web Developer toolbar. Open the webpage in question, then click on the forms button on the Web Developer toolbar > View form information. This will give you the IDs for each control.

Share this post


Link to post
Share on other sites

You will need to get the control's IDs. I've messed with doing this, but I found it difficult to do. One thing that will help is using FireFox and using a addin called Web Developer toolbar. Open the webpage in question, then click on the forms button on the Web Developer toolbar > View form information. This will give you the IDs for each control.

Our application works only on Internet Explorer & is there any alternate method to solve this

Share this post


Link to post
Share on other sites

IE.au3 has tools to help you with this. I strongly suggest you download and use the DebugBar (see my sig) to get the information that you need from the page.

Dale


Free Internet Tools: DebugBar, AutoIt IE Builder, HTTP UDF, MODIV2, IE Developer Toolbar, IEDocMon, Fiddler, HTML Validator, WGet, curl

MSDN docs: InternetExplorer Object, Document Object, Overviews and Tutorials, DHTML Objects, DHTML Events, WinHttpRequest, XmlHttpRequest, Cross-Frame Scripting, Office object model

Automate input type=file (Related)

Alternative to _IECreateEmbedded? better: _IECreatePseudoEmbedded  Better Better?

IE.au3 issues with Vista - Workarounds

SciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=Y Doesn't work needs to be ripped out of the troubleshooting lexicon. It means that what you tried did not produce the results you expected. It begs the questions 1) what did you try?, 2) what did you expect? and 3) what happened instead?

Reproducer: a small (the smallest?) piece of stand-alone code that demonstrates your trouble

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0