Selenium

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.

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.

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.

Accessor is one of the type of Selenese.

I. 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

II. 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 storestrue 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

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

The variable can be used for following reasons:

1) To get the value from an element and comparing with some dynamic value

2) 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

3) To execute some statements in a loop based on the value returned by the element

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.

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.

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

Capabilities of Selenium WebDriver or Google WebDriver or Selenium 2.0 are:

One should use WebDriver when requiring improved support for

1. Mult-browser testing including improved functionality for browsers

not well-supported by Selenium-1.0.

2. Handling multiple frames, multiple browser windows, pop-ups, and alerts.

3. Page navigation.

4. Drag-and-drop.

5. AJAX-based UI elements.

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}

Browsers supported by Selenium RC are:

1. firefox

2. mock

3. firefoxproxy

4. pifirefox

5. chrome

6. iexploreproxy

7. explore

8. firefox3

9. safariproxy

10. googlechrome

11. konqueror

12. firefox2

13. safari

14. piiexplore

15. firefoxchrome

16. opera

17. iehta

18. custom

Operating Systems supported by Selenium are:

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

Assert: Will fail and abort the current test execution.

Verify: Will fail and continue to run the test execution.

StoreEval(script, variable) and storeExpression(expression, variableName).

Five prefixes that Selenium pattern argument are:

glob, regexp, exact, regexpi.

Testing frameworks aren't required, but they can be helpful if QA Tester

wants to automate test cases. Selenium RC supports Bromine, JUnit,

NUnit, RSpec (Ruby), Test::Unit (Ruby), TestNG (Java), unittest (Python).

The Selenium Server 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 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.