Google+

381. Using sendKeys( ) command for entering text into a Password field






In our previous post we've entered text into a 'Username' text box field using the Selenium WebDriver command sendKeys( ). Now lets  enter some text into the password field using the same Selenium WebDriver command sendKeys( ).

Difference between Text Box field and Password field:

Password fields are text fields but the value entered into the password field is not visible to the User as shown below:



Test Description:

Enter the text 'selenium' into the 'Password' password box field using the Selenium WebDriver command sendKeys( ) as shown in the below screenshot:



After going through the test description its very clear that, we have to locate the password text field using CSS path and enter the text 'selenium' into the located password field using sendKeys( ) selenium command.

Lets Implement the Test on Eclipse IDE:

Pre-requisites:

1. Create a new Project say 'WebDriver-Project28' in Eclipse IDE
2. Configure the Project to work with Selenium WebDriver
3. Create a package say 'package28' under the newly created project.
4. Create a Java Class file say 'Class28' under the newly created package as shown below: 





Actual Steps:

1. Write the following code into the newly created Java Class file as shown below and make sure that you resolve all the errors before going to next step:



2. Write the test method 'enterTextIntoPasswordField()' which uses CSS Path Statement for locating the Password field as shown below:





3. Save and Run the 'Class28.java' file by selecting the 'JUnit Test' option and ensure that our Automation Test has enter the text 'selenium' into the Password field as shown in the below video:

Watch the below video:

Click here to watch the video.

Download this Project:


Click here to download this project and import into Eclipse IDE  on your machine.



Please comment below to feedback or ask questions.

Using sendKeys( ) command for entering text into a Text Area field   will be explained in the next post.


 

No comments: