2. •Selenium IDE is a plug-in to Firefox to record and playback tests (like
WinRunner, QTP).
•You can then export the recorded test in most language e.g. HTML, Java ,
.NET , Perl , Ruby etc.
•The exported test can be run in any browser and any platform using
"selenium remote control".

3. • You can use Selenium-Core and customize
everything – deprecated.
• But it is easier to just get a Firefox plug-in
“Selenium-IDE” that helps you “record” test
Cases.
• You can record how an app is being used and then
playback those recordings followed by asserts.
• Get everything at: www.openqa.org/selenium/

4. •Test Runner Mode
 test cases in HTML tables
•Record-Playback mode (Selenium IDE)
•Selenium Remote Control (RC) Mode
 test-cases in your language of choice

5. • Integrated Development Environment for building Selenium test cases.
• Operates as a Firefox add-on and provides an interface for developing and
running individual test cases or entire test suites.
• Selenium-IDE has a recording feature, which will keep account of user actions as
they are performed and store them as a reusable script to play back.
• It also has a context menu (right-click) integrated with the Firefox browser, which
allows the user to pick from a list of assertions and verifications for the selected
location.
• Offers full editing of test cases.
• Although it is a Firefox only add-on, tests created in it can also be run against
other browsers by using Selenium-RC & specifying the name of the test suite on
the command line.

6. • Selenium-RC provides an API (Application Programming
Interface) and library for each of its supported
languages: HTML, Java, C#, Perl, PHP, Python, and Ruby.
• This ability to use Selenium-RC with a high-level
programming language to develop test cases also allows
the automated testing to be integrated with a project’s
automated build environment.

7. Selenium-Grid allows the Selenium-RC solution to scale for
test suites or test suites to be run in multiple environments.
• With Selenium-Grid multiple instances of Selenium-RC are
running on various operating system and browser
configurations, each of these when launching register with a
hub. When tests are sent to the hub they are then redirected
to an available Selenium-RC, which will launch the browser
and run the test.
• This allows for running tests in parallel, with the entire test
suite theoretically taking only as long to run as the longest
individual test.

8. 1) Begin: write and run tests in Firefox.
Selenium IDE is a Firefox add-on that records clicks, typing, and
other actions to make a test, which you can play back in the
browser.
2) Customize: your language, your browser.
Selenium Remote Control (RC) runs your tests in multiple
browsers and platforms. Tweak your tests in your preferred
language.
3) Deploy: scale out, speed up
Selenium Grid extends Selenium RC to distribute your tests across
multiple servers, saving you time by running tests in parallel.

9. * Tests developed on Firefox via Selenium-IDE can be executed on any other supported
browser via a simple Selenium-RC command line.
Browser Selenium-IDE Selenium-RC Operating Systems
1.0 Beta-1 & 1.0 Beta-2:
Firefox 3 Start browser, run tests Windows, Linux, Mac
Record and playback tests
1.0 Beta-1: Record and
Firefox 2 Start browser, run tests Windows, Linux, Mac
playback tests
IE 8 Under development Windows
Test execution only via
IE 7 Start browser, run tests Windows
Selenium-RC
Test execution only via
Safari 3 Start browser, run tests Mac
Selenium-RC
Test execution only via
Safari 2 Start browser, run tests Mac
Selenium-RC
Test execution only via
Opera 9 Start browser, run tests Windows, Linux, Mac
Selenium-RC
Test execution only via
Opera 8 Start browser, run tests Windows, Linux, Mac
Selenium-RC
Test execution only via
Google Chrome Start browser, run tests Windows
Selenium-RC(Windows)
Test execution only via
Others Partial support possible As applicable
Selenium-RC

10. 1) Actions are commands that generally manipulate the state of the
application. They do things like “click this link” and “select that
option”.
• Can be called with “AndWait” suffix, e.g. “clickAndWait”.
2) Accessors examine the state of the application and store the results
in variables, e.g. “storeTitle”.
• They are also used to automatically generate Assertions.
3) Assertions are like Accessors, but verify that the state of the
application conforms to what is expected. Eg. “make sure the page
title is X”, “verify that this checkbox is checked”.
• All Selenium Assertions can be used in 3 modes:
“assert”, “verify”, and ” waitFor”. For example, you can
“assertText”, “verifyText” and “waitForText”.

11. The list of
actions in the
actual test
case
to execute
The root of web
application you
want to test
The log of the
events that were
executed, including
any errors or
warning that may
have occurred

12. Execution Record test
Commands actions
Try the test in
the Web based
TestRunner
Reference of the
currently selected
command Specify commands,
including asserts

13. Chris Pederick's Web Developer toolbar
XPather
Firebug
Xpath Checker