Hello Sir ,
--
You received this message because you are subscribed to the Google Groups
"Selenium Users" group.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to
selenium-user...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/selenium-users?hl=en.
--
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
If you have received this email in error please notify postm...@ardescosolutions.com
The validator will check if your HTML is W3C compliant. If it is not it will show you any errors.
If you have broken HTML you will have a broken DOM, modern browsers try to fix it on the fly but they are into guesswork territory where each browser will guess differently with varying degrees of success. Just because you can find one text field is no guarantee that you will be able to find any others if your markup is invalid (the browser may have guessed one field correctly but got the other one wrong).
The xpath you have supplied is looking for a paragraph, not an input box. A valid xpath would be:
//input[@id=’password’]
Check to see if that works.
If none of this helps you will need to show us your test script.
Object for which execution will be done is Password ( According to my script)
Set 'Password' as '*********'
Try not to key into classes as they change, an ID is the most secure way of finding an element using XPath. The one I supplied below should work, does it?
You have still not told us if you have run the page in question through a validator to see if it is valid HTML and we cannot give you any more help unless you supply your test script (the HTML of the page you are testing may be useful as well).
I find the easiest way to get round issues like that are to download and use the Web Developer toolbar in FireFox, one of the options it gives you is validate local HTML so the validator doesn’t need to have access to the website you are testing it will just take a copy of the page and send it over to the validator.
The validator is also downloadable so that you can run an instance locally on your network if required. I would strongly suggest that any company making websites should do this as a basic W3C validation will throw up lots of potential problems that can easily be fixed with minimal effort.
Can you provide your test script? If you do we can see what you are trying to do and try to find an answer for you.
Please have a look at it. Password is not getting enetered into the text field.
I’ve had a quick look through this and I can’t see where in your test you are trying to interact with the input element with an id of password , in fact the majority of what you have supplied appears to be extracting data from an Excel spread sheet.
Where is the code for your test?