Explore topic-wise InterviewSolutions in .

Using Recording FEATURE we can GENERATE Test CASES otherwise we can type Test STEPS using ELEMENT locators and Selenese commands.

Using Recording feature we can generate Test cases otherwise we can type Test steps using Element locators and Selenese commands.

.html

.html

• When an "assert" COMMAND fails then TEST execution will be ABORTED.
• When a "VERIFY" command fails then test will CONTINUE execution and logging the failure.

USING Breakpoints and Step command we can EXECUTE Selenium TEST CASE step by step.

Using Breakpoints and Step command we can execute Selenium Test case step by step.

Yes, we can edit recorded TEST CASES, Add Steps, DELETE steps, edit steps and INSERT COMMENTS.

Yes, we can edit recorded Test cases, Add Steps, Delete steps, edit steps and Insert comments.

Important Commands are:

OPEN, click, type, SELECT, assertText, assertTitle, assertTextPresent, verifyText, verifyTextPresent, veriftTitle, waitForText, waitForTextPresent, waitForTitle, store, storeText, storeTitle, CHECK, UNCHECK, pause, mouseover, ETC...

Important Commands are:

Open, click, type, select, assertText, assertTitle, assertTextPresent, verifyText, verifyTextPresent, veriftTitle, waitForText, waitForTextPresent, waitForTitle, store, storeText, storeTitle, check, uncheck, pause, mouseover, etc...

OPEN the Test case in SELENIUM IDE,

• File menu
• Save Test SUITE As
• Select the language you want to export your test and provide the name to save it.

Open the Test case in Selenium IDE,

STEPS to Download and Install Selenium IDE:

• LAUNCH Firefox browser, download selenium IDE from the Seleniumhq.org website.
• Firefox will protect you from INSTALLING add ons from unfamiliar LOCATIONS, so we will need to click "Allow" to proceed with the installation.
• Install multiple ITEMS to support Java, Ruby, Python etc... formats. 
• Restart Firefox browser.
• After Firefox reboots then we can use Selenium IDE.

Steps to Download and Install Selenium IDE:

 It has Record and PLAYBACK FEATURES to create and execute TEST cases

• User/Tester can type Test steps using element locators and Selenese commands without using Recording FEATURE.
• Debugging feature for debugging test cases.
• It has an option of asserting title of every page automatically.
• Option to RUN single test or multiple tests(Test suite).
• It has a feature of exporting testcase/suite into different formats like C#, Java, Ruby, Python

 It has Record and Playback features to create and execute Test cases

* SYMBOL MEANS any CHARACTER

* symbol means any character

SELENIUM IDE is firefox ad on, so it RUNS on Firefox browser.

Selenium IDE is firefox ad on, so it runs on Firefox browser.

That TRIANGLE INDICATES that test PAUSED at that STEP, or will start from that step.

That triangle indicates that test paused at that step, or will start from that step.

We need to SET a BREAK point in the TEST, so the test will PAUSE at the break point.

We need to set a break point in the test, so the test will pause at the break point.

Absolute URL means the URL starts with http or HTTPS. Selenium IDE addes the argument in the open STATEMENT and create an absolute URL

RELATIVE URL means that in BaseURL, we can put the main domain, and in the open STATMENT, USER should put relative URL; 

For example, if main url is http://mysite.com, in the relative url, we can put http://beta.mysite.com in the open statement.

Absolute URL means the URL starts with http or https. Selenium IDE addes the argument in the open statement and create an absolute URL

Relative URL means that in BaseURL, we can put the main domain, and in the open statment, user should put relative URL; 

For example, if main url is http://mysite.com, in the relative url, we can put http://beta.mysite.com in the open statement.

${variableName}

${variableName}

USE "STORE" COMMAND

Use "store" command

In the SELENIUM IDE options, CHECK "RECORD Absolute URL" option.

In the Selenium IDE options, check "Record Absolute URL" option.

In the BROWSER, the TEST name in Selenium IDE will be DISPLAYED. 

In the browser, the test name in Selenium IDE will be displayed. 

Users can USE "Play current test CASE" FUNCTION of Selenium IDE

Users can use "Play current test case" function of Selenium IDE

The limitations of Selenium IDE are:

1. Selenium IDE uses only HTML language
2. Conditional or branching statements execution like using of if, select statements is not possible
3. Looping statements using is not possible directly in Selenium HTML language in ide
4. READING from external FILES like .txt, .xls is not possible
5. Reading from the external DATABASES is not possible with ide
6. Exceptional handling is not there
7. A neat formatted Reporting is not possible with ide

To eliminate the above ISSUES we use Selenium RC

The limitations of Selenium IDE are:

To eliminate the above issues we use Selenium RC

1. Open user-EXTENSIONS.js with an editor (Notepad, etc.); it’s found in the seleniumcorescripts folder. If it doesn’t exist, just CREATE it.
2. If you need to, commit the user-extensions.js file (like if you use SUBVERSION).
3. Open Selenium IDE and choose the Options menu and then Options… from that menu.
4. Make sure the path to your user-extensions.js file is entered in the Selenium Core extensions field (like seleniumcorescriptsuser-extensions.js)
5. Press OK button on options
6. Restart the IDE to reflect your extensions.

NOTE: After reopen, Selenium IDE may SHOW compilations errors if the user-extensions.js file has any syntax errors.

Note: After reopen, Selenium IDE may show compilations errors if the user-extensions.js file has any syntax errors.

captureEntirePageScreenshot :

1. This captures the AUT web PAGE only
2. This SUPPORTS only mozilla firefox
3. Accepts two arguments. one is the file name to be SAVED and other argument is BACK ground color

CaptureScreenShot :

1. This captures the System screen SHOT
2. This supports all the browsers when you run from Selenium RC
3. Accepts one argument. That is the file name to be saved.

captureEntirePageScreenshot :

CaptureScreenShot :

captureEntirePageScreenshot : Saves the entire contents of the CURRENT window canvas to a PNG file. Contrast this with the captureScreenshot command, which captures the contents of the OS VIEWPORT (i.e. whatever is CURRENTLY being displayed on the monitor), and is IMPLEMENTED in the RC only. Currently this only works in Firefox when running in chrome mode, and in IE non-HTA using the EXPERIMENTAL “Snapsie” utility. The Firefox implementation is mostly borrowed from the Screengrab! Firefox extension. 

captureEntirePageScreenshotAndWait : Saves the entire contents of the current window canvas to a PNG file. Contrast this with the captureScreenshot command, which captures the contents of the OS viewport (i.e. whatever is currently being displayed on the monitor), and is implemented in the RC only. Currently this only works in Firefox when running in chrome mode, and in IE non-HTA using the EXPERIMENTAL “Snapsie” utility. The Firefox implementation is mostly borrowed from the Screengrab! Firefox extension.

Note: This command runs with only mozilla firefox when you RUN the tests from RC. Other browsers it will not support

captureEntirePageScreenshot : Saves the entire contents of the current window canvas to a PNG file. Contrast this with the captureScreenshot command, which captures the contents of the OS viewport (i.e. whatever is currently being displayed on the monitor), and is implemented in the RC only. Currently this only works in Firefox when running in chrome mode, and in IE non-HTA using the EXPERIMENTAL “Snapsie” utility. The Firefox implementation is mostly borrowed from the Screengrab! Firefox extension. 

captureEntirePageScreenshotAndWait : Saves the entire contents of the current window canvas to a PNG file. Contrast this with the captureScreenshot command, which captures the contents of the OS viewport (i.e. whatever is currently being displayed on the monitor), and is implemented in the RC only. Currently this only works in Firefox when running in chrome mode, and in IE non-HTA using the EXPERIMENTAL “Snapsie” utility. The Firefox implementation is mostly borrowed from the Screengrab! Firefox extension.

Note: This command runs with only mozilla firefox when you run the tests from RC. Other browsers it will not support

Bitmaps are captured using the SELENIUM set of commands. There are two modes of capturing the bitmaps

1. Capture the bitmap for the entire PAGE – it captures the browser MAIN page AREA of AUT
2. Capture the bitmap for the screen shots – it captures the entire screen shot like the print scree that you give from your keyboard

Selenium doesn’t support bitmap capturing for an element on AUT.

Bitmaps are captured using the Selenium set of commands. There are two modes of capturing the bitmaps

Selenium doesn’t support bitmap capturing for an element on AUT.

Accessors are mostly used for storing the value in a VARIABLE.

The variable can be used for following reasons:

• To GET the value from an element and comparing with some dynamic value
• To take a logical decision to execute the test STEPS
• EX: if the value of the variable true execute step1 and step2 else step3 and step4
•  To execute some statements in a loop BASED on the value returned by the element

Accessors are mostly used for storing the value in a variable.

The variable can be used for following reasons:

ACCESSOR is one of the type of Selenese.

• Accessors are used for storing the VALUE of a target in a variable.

Ex:

1. storeTitle – Stores the TITLE of a window in a variable
2. storeText – Stores the target ELEMENT text in a variable

• Accessors are also used for evaluating the result and storing the result in a variable

Ex: storeTextPresent – Evaluates whether the text is present in the current window. If the text is present stores true in the variable else stores FALSE

Ex: storeEementPresent – Evaluates whether the element is present in the current window. If the element is present stores true in the variable else stores false

Accessor is one of the type of Selenese.

Ex:

Ex: storeTextPresent – Evaluates whether the text is present in the current window. If the text is present stores true in the variable else stores false

Ex: storeEementPresent – Evaluates whether the element is present in the current window. If the element is present stores true in the variable else stores false

1. ASSERT – If the expected value is mandatory to continue with the NEXT set of STEPS we will use Assert. As Assert aborts the test, if the expected value doesn’t match. It is GOOD to use for any mandatory checks.
2. verify – If the expected value is optional to continue with the next set of steps we will use Verify. As Verify continues executing with the next set of steps, if the expected value doesn’t match. It is good to use for any optional checks.
3. waitFor – If your test needs to wait, if the expected value is not matching we use waitFor. We normally use waitFor for AJAX kind of controls loading within a PAGE

Selenium Assertions can be used in 3 modes:

1. assert – When an “assert” fails, the test will be aborted. If you are executing test suite, the next state case will start
2. verify – When a “verify” fails, the test will continue execution, logging the failure.
3. waitFor – “waitFor” commands wait for some condition to BECOME TRUE (which can be useful for testing Ajax applications). They will succeed immediately if the condition is already true. However, they will fail and halt the test if the condition does not become true WITHIN the CURRENT timeout setting

Selenium Assertions can be used in 3 modes:

• Assertion is nothing but a check or verification point.
• Assertion verifies the STATE of the application conforms to what is expected.
• Examples include “MAKE sure the PAGE title is X” and “verify that this checkbox is CHECKED.

Check points or VERIFICATION points are KNOWN as Assertions in SELENIUM. The keywords with below mentioned prefix will be USED for adding check points or verification points.

1. verify
2. assert
3. waitFor

Check points or verification points are known as Assertions in Selenium. The keywords with below mentioned prefix will be used for adding check points or verification points.

Selenium set of commands which are USED for running the TEST are CALLED as Selenese.

There are three types of Selenese, those are:

1. Actions – used for performing the operations and INTERACTIONS with the target ELEMENTS
2. Assertions – used as check points
3. Accessors – used for storing the values in a variable

Selenium set of commands which are used for running the test are called as Selenese.

There are three types of Selenese, those are:

Selenium REGULAR EXPRESSION patterns offer the same wide array of special characters that exist in JavaScript.

Below are a subset of those special characters:

.: any single character

[ ]character class: any single character that appears inside the brackets

*quantifier: 0 or more of the preceding character (or GROUP)

+quantifier: 1 or more of the preceding character (or group)

?quantifier: 0 or 1 of the preceding character (or group)

{1,5}quantifier: 1 through 5 of the preceding character (or group)

|alternation: the character/group on the LEFT or the character/group on the right

( )grouping: often used with alternation and/or quantifier

Selenium regular expression patterns offer the same wide array of special characters that exist in JavaScript.

Below are a subset of those special characters:

.: any single character

[ ]character class: any single character that appears inside the brackets

*quantifier: 0 or more of the preceding character (or group)

+quantifier: 1 or more of the preceding character (or group)

?quantifier: 0 or 1 of the preceding character (or group)

{1,5}quantifier: 1 through 5 of the preceding character (or group)

|alternation: the character/group on the left or the character/group on the right

( )grouping: often used with alternation and/or quantifier

Regular expressions in Selenium IDE can be used with the keyword – REGEXP: as a prefix to the value and patterns NEEDS to be included for the expected values.

For example if you want to use the regular expression for a command

Command: verifyText
Target: //font/font/b/font[1]
Value: FLIGHT Confirmation # 2011-05-02451

in the above example Flight Confirmation is continuously CHANGING each time you run the test case. So this can be written with a regular expression as mentioned below

Command: verifyText
Target: //font/font/b/font[1]
Value: regexp:Flight Confirmation # [0-9]{4}-[0-9]{2}-[0-9]{5,10}

Regular expressions in Selenium IDE can be used with the keyword – regexp: as a prefix to the value and patterns needs to be included for the expected values.

For example if you want to use the regular expression for a command

Command: verifyText
Target: //font/font/b/font[1]
Value: Flight Confirmation # 2011-05-02451

in the above example Flight Confirmation is continuously changing each time you run the test case. So this can be written with a regular expression as mentioned below

Command: verifyText
Target: //font/font/b/font[1]
Value: regexp:Flight Confirmation # [0-9]{4}-[0-9]{2}-[0-9]{5,10}

There are three types of PATTERNS available in Selenium:

1. GLOBBING
2. regular expressions
3. EXACT

There are three types of patterns available in Selenium:

The Selenium Server which launches and kills browsers, and acts as an HTTP proxy for browser requests.

Client LIBRARIES for various programming LANGUAGES, each of which instructs the Selenium Server in how to test the AUT by passing it your test script’s Selenium commands.

The DIAGRAM shows the client libraries communicate with the Server passing each Selenium command for execution. Then the server passes the Selenium command to the browser USING Selenium-Core JavaScript commands. The browser, using its JavaScript interpreter, executes the Selenium command, which effectively, RUNS the check you specified in your Selenese test script.

The Selenium Server which launches and kills browsers, and acts as an HTTP proxy for browser requests.

Client libraries for various programming languages, each of which instructs the Selenium Server in how to test the AUT by passing it your test script’s Selenium commands.

The diagram shows the client libraries communicate with the Server passing each Selenium command for execution. Then the server passes the Selenium command to the browser using Selenium-Core JavaScript commands. The browser, using its JavaScript interpreter, executes the Selenium command, which effectively, runs the check you specified in your Selenese test script.

One should use WebDriver when REQUIRING improved support for

• Mult-BROWSER testing including improved functionality for browsers not well-supported by Selenium-1.0.
• HANDLING multiple frames, multiple browser WINDOWS, POPUPS, and alerts.
• Page navigation.
• Drag-and-drop.
• AJAX-based UI elements.

One should use WebDriver when requiring improved support for

WebDriver uses a different underlying framework from Selenium’s javascript Selenium-Core. It ALSO provides an alternative API with functionality not supported in Selenium-RC. WebDriver does not DEPEND on a javascript core embedded within the browser, therefore it is able to avoid some long-running Selenium limitations.

WebDriver’s goal is to provide an API that establishes:

• A well-designed standard programming interface for web-app TESTING.
• Improved consistency between browsers.
• Additional functionality addressing testing problems not well-supported in Selenium 1.0.

The Selenium developers strive to continuously improve Selenium. Integrating WebDriver is another step in that PROCESS. The developers of Selenium and of WebDriver felt they could make SIGNIFICANT gains for the Open Source test automation community be combining forces and merging their ideas and technologies. Integrating WebDriver into Selenium is the current result of those efforts.

WebDriver uses a different underlying framework from Selenium’s javascript Selenium-Core. It also provides an alternative API with functionality not supported in Selenium-RC. WebDriver does not depend on a javascript core embedded within the browser, therefore it is able to avoid some long-running Selenium limitations.

WebDriver’s goal is to provide an API that establishes:

The Selenium developers strive to continuously improve Selenium. Integrating WebDriver is another step in that process. The developers of Selenium and of WebDriver felt they could make significant gains for the Open Source test automation community be combining forces and merging their ideas and technologies. Integrating WebDriver into Selenium is the current result of those efforts.

Selenium GRID is part of Selenium suite of projects. Selenium Grid transparently distribute your tests on multiple machines so that you can run your tests in parallel, cutting down the time required for running in-browser test suites. This will DRAMATICALLY SPEEDS up in-browser web testing, giving you quick and accurate feedback you can rely on to IMPROVE your web application.

Selenium Grid is part of Selenium suite of projects. Selenium Grid transparently distribute your tests on multiple machines so that you can run your tests in parallel, cutting down the time required for running in-browser test suites. This will dramatically speeds up in-browser web testing, giving you quick and accurate feedback you can rely on to improve your web application.

The LANGUAGES supported by Selenium RC:

1. .Net,
2. JAVA (JUNT 3, Junt 4, TestNG, Groovy)
3. PERL,
4. Python,
5. PHP,
6. Ruby

The languages supported by Selenium RC:

Selenium-IDE does not directly support:

1. condition statements
2. iteration
3. logging and reporting of test results
4. error handling, particularly unexpected errors
5. database testing
6. test case grouping
7. re-execution of FAILED tests
8. test case dependency
9. capture screenshots on test failures

The reason BEHIND why Selenium-IDE does not support the above mentioned REQUIREMENTS is IDE supports only HTML language. Using HTML language we cannot achieve the above mentioned requirements. Because HTML does not support conditional, looping and external source connectives.

To overcome the above mentioned problems Selenium RC is used.

Since Selenium RC supports the languages .Net, Java, Perl, Python, PHP, and Ruby. In these languages we can WRITE the programme to achieve the IDE issues

Selenium-IDE does not directly support:

The reason behind why Selenium-IDE does not support the above mentioned requirements is IDE supports only HTML language. Using HTML language we cannot achieve the above mentioned requirements. Because HTML does not support conditional, looping and external source connectives.

To overcome the above mentioned problems Selenium RC is used.

Since Selenium RC supports the languages .Net, Java, Perl, Python, PHP, and Ruby. In these languages we can write the programme to achieve the IDE issues

Selenium-RC is the solution for tests that need a little more than just simple browser actions and a linear execution. Selenium-RC leverages the FULL power of programming languages, creating tests that can do things like read and write EXTERNAL files, make queries to a database, send emails with test REPORTS, and practically anything else a user can do with a normal APPLICATION.

You will want to use Selenium-RC WHENEVER your test requires logic not supported by running a script from Selenium-IDE

Selenium-RC is the solution for tests that need a little more than just simple browser actions and a linear execution. Selenium-RC leverages the full power of programming languages, creating tests that can do things like read and write external files, make queries to a database, send emails with test reports, and practically anything else a user can do with a normal application.

You will want to use Selenium-RC whenever your test requires logic not supported by running a script from Selenium-IDE

Selenium IDE

WORKS in Firefox 2+ Start browser, run tests Run tests

Operating Systems Supported:

1. WINDOWS,
2. OS X
3. Linux
4. Solaris
5. Others whichever supports Firefox 2+

Selenium Remote Control

Used for starting browser and run tests

Operating Systems Supported:

1. Windows,
2. OS X
3. Linux
4. Solaris
5. Others

Selenium Core

Used for running tests

Operating Systems Supported:

1. Windows,
2. OS X
3. Linux
4. Solaris
5. Others

Selenium IDE

Works in Firefox 2+ Start browser, run tests Run tests

Operating Systems Supported:

Selenium Remote Control

Used for starting browser and run tests

Operating Systems Supported:

Selenium Core

Used for running tests

Operating Systems Supported:

Supported browsers for Selenium RC include:

1. *FIREFOX
2. *MOCK
3. *firefoxproxy
4. *pifirefox
5. *chrome
6. *iexploreproxy
7. *iexplore
8. *firefox3
9. *safariproxy
10. *googlechrome
11. *KONQUEROR
12. *firefox2
13. *SAFARI
14. *piiexplore
15. *firefoxchrome
16. *OPERA
17. *iehta
18. *custom

Supported browsers for Selenium RC include:

The command used for displaying the values of a VARIABLE into the output console or log – ECHO 
If you want to DISPLAY a constant string.

The below mentioned command can be used
echo <constant string>
ex: echo “The SAMPLE message”
If you want to display the VALUE of a variable it can be written like below
echo ${<variable name>>
ex: echo ${var1}
Note: Here var1 is the variable

The command used for displaying the values of a variable into the output console or log – echo 
If you want to display a constant string.

The below mentioned command can be used
echo <constant string>
ex: echo “The sample message”
If you want to display the value of a variable it can be written like below
echo ${<variable name>>
ex: echo ${var1}
Note: Here var1 is the variable

From selenium IDE the test suites can be exported into the LANGUAGES as mentioned below

1. .NET
2. Java
3. Perl
4. Python
5. PHP
6. Ruby

The below mentioned steps can explain how to EXPORT the test suites:

• Open the test case from Selenium IDE
• Select File -> Export Test Suite As

From selenium IDE the test suites can be exported into the languages as mentioned below

The below mentioned steps can explain how to export the test suites:

From SELENIUM IDE the test cases can be EXPORTED into the languages

1. .Net
2. JAVA
3. Perl
4. Python
5. PHP
6. Ruby

The below MENTIONED steps can explain how to export the test cases:

1. Open the test case from Selenium IDE
2. Select File -> Export Test Case As

From selenium IDE the test cases can be exported into the languages

The below mentioned steps can explain how to export the test cases:

To debug or execute the test CASES line by line.

Follow the below MENTIONED STEPS:

1. Insert a BREAK From the location where you want to execute step by step
2. Run the test case
3. Execution will be paused at the given break point
4. Click on the step (Blue) button to continue with the next statement
5. Click on Run button, to continue EXECUTING all the commands at a time

To debug or execute the test cases line by line.

Follow the below mentioned steps:

BREAK point can be set in TWO ways in Selenium IDE

1. Right click on the command in Selenium IDE and select “Toggle Break Point”
2.  Select the command in Selenium IDE and PRESS “B” KEY on the keyboard

• If you want to clear the break point once again Spress “B” key on the keyboard
• You can set multiple break points in Selenium IDE

Break point can be set in two ways in Selenium IDE

Comments in Selenium IDE can be set in two ways:

1. Right click on the command in Selenium IDE and select “Inert New COMMENT”
2. If you want to comment an existing line. You NEED to follow the below mentioned steps.

• Select the source tab in IDE
• Select the line which you want to comment
• Assume that if you want to comment a open command you need to write like below mentioned code

<tr&GT;
<!–
<td>open&AMP;l/td>
<td>/node/304/edit&l/td>
<td></td>
–>
</tr>

Comments in Selenium IDE can be set in two ways:

<tr>
<!–
<td>open&l/td>
<td>/node/304/edit&l/td>
<td></td>
–>
</tr>

Start point SELENIUM IDE can be set in two ways:

1. Right click on the command in Selenium IDE and select “Set / CLEAR Start Point”
2. Select the command in Selenium IDE and press “S” KEY on the keyboard

• You can have only one start point
• If you have already set one start point and you selected other command as start point. Then the first start point will be REMOVED and the new start point will be set

Start point Selenium IDE can be set in two ways: