Learn about Selenium WebDriver to create cross-browser tests, explore 170+ recipes, and discover techniques for automating user interactions efficiently across various browsers. Gain valuable automation skills.

tarballFinal.tar.gz

ch2_les2

ch2_les3

ch3_les2

ch3_les3

ch3_les4

ch4_1

ch4_3

ch4_4

ch5_1

ch5_2

ch6_2

ch6_1

7_uncheck

7_icheck

10-1

10-2

11-1

11-2

12-1

12-2

12-3

13-1

13_jPop

13_modal_dialog

14_print_text

14_screenshot

15_alphabetic

15_alphanumeric

15_misc

15_numeric

16_authentication

16_browser_profiles

16_download

17_keyboard

17_mouse

18_angular

18_canvas

18_email_time

18_ember

18_geolocation

18_js_event

dec24_ch16-1

18_select2

7_check

ch_19

ch_20-1

ch_20-2

ch_20-3

ch_21-1-1

ch_21-1-2

ch_21-1-3

ch_21-2

ch_22-1

ch_22-2

ch_23

headless

19-Htmleditors

7-uncheck2

7-check

7-custom-check

9-browser

9-navigation

9-browser_advance

11-frame

11-iframe

13-fileUpload

13-jPop

13-modal_dialog

17-keyboard

17-mouse

Selenium WebDriver is a powerful web framework that allows you to execute cross-browser tests. By learning this tool, you can create robust, browser-based regression automation suites and tests, all while scaling and distributing scripts across many different environments.

This is a recipe course, meaning you can directly go to the part that interests you. For example, if you are testing a multiple select list and don’t know how, you can look it up in the course roadmap and proceed with that lesson.

With over 170 recipes for web application testing, you’ll have the opportunity to learn and practice both beginning and advanced techniques with Selenium WebDriver. By the time you complete this course, you will have a great new skill, and you’ll save tons of time when it comes to automating real user interactions in Firefox, Safari, Edge, Chrome, Internet Explorer and more!

Selenium WebDriver Recipes in Node.js

One of the reasons for Selenium commercial success is its ability to program. Unlike many other testing tools, which only provides record-and-playback functionalities, Selenium offers programming. This makes not only automated test scripts much more maintainable but also more flexible. In the upcoming lessons, we will explore some examples that will make use of programming practices to help our testing needs.

In the upcoming lessons, we will practice various concepts and techniques of leverage programming.  


![](/api/collection/10370001/6497270816571392/page/4849122947891200/image/5660037429592064)

# Raising exceptions to fail a test

An exception means an occurrence of an anomalous or exceptional condition, and the code to handle these exceptions is called exception handling. Exception handling is an important aspect of programming. If an exception is not handled properly, the program will terminate execution and the exception will be displayed. A standard way of handling exceptions in JavaScript is shown below:


~~~    
try {
  driver.actions.sendKeys("TestWise").perform();
} catch (err) {
  console.log("Error occurred: " + err);
} finally { 
  console.log("Clean up");
  driver.quit();
}
~~~

The above scripts exit successfully with the output:


~~~x
Error occurred: TypeError: driver.actions.sendKeys is not a function
Clean up
~~~

Here, the `catch` block is handling the exception and if the exception is handled, the program will continue. Otherwise, the `ex.printStackTrace()` method will print out the stack trace of the exception. The `finally` block always runs whether the exceptions are thrown from the `try` block or not.

In Selenium, we use JavaScript Promises for exception handling as:

~~~
driver.findElement(By.name("user")).sendKeys("bomb").then(null, function(err) {
  if (err.name == "NoSuchElementError") {
     console.log("Error: " + err);
  }
});
~~~


Though the `assert` provides most of the assertions needed, we can raise exceptions too. 

~~~    
if (process.platform != "darwin" && process.platform != "linux") {
  throw("Unsupported platform: " + process.platform);
}
~~~

In test output (when running on Windows):

~~~x
Error: done() invoked with non-Error: Unsupported platform: win32
~~~

In addition to this, exceptions can be raised for non-assertion purposes as well like:

## Flag incomplete tests


The problem with “TO-DO” comments is that we might forget them.

 ~~~
   test.it("Foo", function() {
		 // TODO 
   });
   ~~~
So, the better way is to use `throw()`:
 ~~~    
   test.it("Foo", function() {
     throw("TO BE DONE");
   });
~~~

## Stop test execution during debugging a test

Sometimes, we utilize automated tests to get to a certain page in the application quickly.

~~~
   // test steps ...
throw("Stop here, I take over from now. I delete this later.")
~~~   



Discover what you can do with programming, and learn how to raise an exception for test failure.

Why Programming?

Getting Started

Working with Locators

Working with Hyperlinks

Working with Buttons

Working with Text Fields and Areas

Working with Radio Buttons and Radio Groups

Working with Checkboxes

Working with Select Lists

Page Navigations and Browser Management

Assertions

Working with Frames

Working with AJAX

Working with File Uploads and Pop-Up Dialogs

Debugging Test Scripts

Testing Data

Working with Browser Profiles and Capabilities

Working with Advanced User Interactions

Working with HTML5 and Dynamic Websites

“What You See Is What You Get” HTML Editors

Leverage Programming

Optimizations

Gotchas

Appendix A: Miscellaneous

Appendix B: Installations

Wrapping Things Up

Why Programming?

Introduction