KaneAI - World’s First E2E Software Testing Agent.Book a Demo Join TestMu Conference

Selenium

View Documentation

View sample repo

Selenium automation testing framework index.

Description
Support
Code statistics
License
Downloads
Package and Class index

Test More In Less Time

Run Automation Testing In Parallel On The LambdaTest Cloud

Start for free

Description

Selenium is one of the most renowned open-source test automation frameworks. It allows test automation of web-apps across different browsers & operating systems.

Support and updates

Selenium has 24100 stars, 7044 forks.
It has 2 major releases in the past 6 months.
It has 22 commits and there are 20 open pull requests.
It has 113 open issues and 8142 have been closed.

Code statistics

Selenium has 70 packages.
Selenium has 807 methods.

Blogs

Check out the latest blogs from LambdaTest on this topic:

Top 17 Software Testing Blogs to Look Out For in 2019

Software testing is one of the widely aspired domain in the current age. Finding out bugs can be a lot of fun, and not only for testers, but it’s also for everyone who wants their application to be free of bugs. However, apart from online tutorials, manuals, and books, to increase your knowledge, find a quick help to some problem or stay tuned to all the latest news in the testing domain, you have to rely on software testing blogs. In this article, we shall discuss top 17 software testing blogs which will keep you updated with all that you need to know about testing.

What is a WebView And How To Test It?

Convenience is something that we can never be fully satisfied with. This is why software developers are always made to push their limits for bringing a better user experience, without compromising the functionality. All for the sake of saving the churn in today’s competitive business. People are greedy for convenience and this is why Hybrid applications have been so congenial in the cyber world.

Manual Testing vs Automation Testing: Check Out The Differences

The most arduously debated topic in software testing industry is What is better, Manual testing or Automation testing. Although Automation testing is most talked about buzzword, and is slowly dominating the testing domain, importance of manual testing cannot be ignored. Human instinct can any day or any time, cannot be replaced by a machine (at least not till we make some real headway in AI). In this article, we shall give both debating side some fuel for discussion. We are gonna dive a little on deeper differences between manual testing and automation testing.

Common Challenges In Selenium Automation & How To Fix Them?

Selenium is one of the most popular test frameworks which is used to automate user actions on the product under test. Selenium is open source and the core component of the selenium framework is Selenium WebDriver. Selenium WebDriver allows you to execute test across different browsers like Chrome, Firefox, Internet Explorer, Microsoft Edge, etc. The primary advantage of using the Selenium WebDriver is that it supports different programming languages like .Net, Java, C#, PHP, Python, etc. You can refer to articles on selenium WebDriver architecture to know more about it.

10 Ways To Avoid Cross-Browser Compatibility Issues

This article is a part of our Content Hub. For more in-depth resources, check out our content hub on Cross Browser Testing Tutorial.

Automation Testing Tutorials

Learn to execute automation testing from scratch with LambdaTest Learning Hub. Right from setting up the prerequisites to run your first automation test, to following best practices and diving deeper into advanced test scenarios. LambdaTest Learning Hubs compile a list of step-by-step guides to help you be proficient with different test automation frameworks i.e. Selenium, Cypress, TestNG etc.

LambdaTest Learning Hubs:

YouTube

You could also refer to video tutorials over LambdaTest YouTube channel to get step by step demonstration from industry experts.

License

Selenium is lincensed under the Apache License 2.0

LambdaTest Community Discussions

Ask and answer questions on LambdaTest community. Visit now!

StackOverFlow community discussions

Questions

Discussion

Is there a way to automate IE Mode in Microsoft Edge browser for project in Ruby?

How do I extract the Selenium Element from a Capybara Element?

cucumber re-run failed scenarios automatically with a tag?

Setting "Accept-Language" header in watir-webdriver and phantomjs

Undefined method `^' for String (NoMethodError)

Failed to open TCP connection to 127.0.0.1:9516 (connection refused)

page object model: why not include assertions in page methods?

How to slow down an in browser test cucumber on ruby

Is there any way to run a capybara server?

Selenium confirm position of cursor

I didn't find related information about using Ruby to automate Edge IE mode. AFAIK, it only works with C#, VB.NET and Python now.

You can have a try to set the same IE capabilities in Ruby, if it doesn't work, then I think Ruby doesn't support the capabilities either. In this situation, you can raise a new issue about adding these features in IE WebDriver on Selenium GitHub as IE WebDriver is maintained by Selenium.

https://stackoverflow.com/questions/68582325/is-there-a-way-to-automate-ie-mode-in-microsoft-edge-browser-for-project-in-ruby

More recent versions of Cucumber have a retry flag

cucumber --retry 2

Will retry tests two times if it fails

https://stackoverflow.com/questions/9833360/cucumber-re-run-failed-scenarios-automatically-with-a-tag

This worked for me:

$ phantomjs -v
1.9.2

$ gem search -l webdriver
*** LOCAL GEMS ***
selenium-webdriver (2.38.0)
watir-webdriver (0.6.4)

$ irb 

irb(main):001:0> require "watir-webdriver"
=> true

irb(main):002:0> capabilities = Selenium::WebDriver::Remote::Capabilities.phantomjs
=> #<Selenium::WebDriver::Remote::Capabilities:0x007fbbeb8faa08 @capabilities={:browser_name=>"phantomjs", :version=>"", :platform=>:any, :javascript_enabled=>true, :css_selectors_enabled=>true, :takes_screenshot=>true, :native_events=>false, :rotatable=>false, :firefox_profile=>nil, :proxy=>nil}>

irb(main):003:0> capabilities['phantomjs.page.customHeaders.Accept-Language'] = 'ru-RU'
=> "ru-RU"

irb(main):004:0> browser = Watir::Browser.new :phantomjs, desired_capabilities: capabilities
=> #<Watir::Browser:0x5be4c6adc1d41736 url="about:blank" title="">

irb(main):005:0> browser.goto "httpbin.org/headers"
=> "http://httpbin.org/headers"

irb(main):006:0> puts browser.html
<html><head></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">{
  "headers": {
    "Accept-Encoding": "gzip",
    "User-Agent": "Mozilla/5.0 (Macintosh; PPC Mac OS X) AppleWebKit/534.34 (KHTML, like Gecko) PhantomJS/1.9.2 Safari/534.34",
    "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8",
    "Connection": "close",
    "Accept-Language": "ru-RU",
    "Host": "httpbin.org"
  }
}</pre></body></html>
=> nil

https://stackoverflow.com/questions/20563465/setting-accept-language-header-in-watir-webdriver-and-phantomjs

I got the same error on MacOs 10.11.6 and the following solved the issue:

Find the chromedriver

~/P/m/web-automation (master ⚡↩) which chromedriver
/Users/mesutgunes/.rbenv/shims/chromedriver

Remove it

rm /Users/mesutgunes/.rbenv/shims/chromedriver

Try to re-link it, follow the instruction:

~/P/m/web-automation (master ⚡↩) brew link chromedriver
Linking /usr/local/Cellar/chromedriver/2.30...
Error: Could not symlink bin/chromedriver
Target /usr/local/bin/chromedriver
already exists. You may want to remove it:
  rm '/usr/local/bin/chromedriver'

To force the link and overwrite all conflicting files:
  brew link --overwrite chromedriver

To list all files that would be deleted:
  brew link --overwrite --dry-run chromedriver

https://stackoverflow.com/questions/41960088/failed-to-open-tcp-connection-to-127-0-0-19516-connection-refused

As a guideline, assertions should be done in tests and not in page objects. Of course, there are times when this isn't a pragmatic approach, but those times are infrequent enough for the above guideline to be right. Here are the reasons why I dislike having assertions in page objects:

It is quite frustrating to read a test that just calls verify methods where assertions are buried elsewhere in page objects. Where possible, it should be obvious what a test is asserting; this is best achieved when assertions are directly in a test. By hiding the assertions somewhere outside of a test, the intent of the test is not so clear.
Assertions in browser tests can be expensive - they can really slow your tests down. When you have hundreds or thousands of tests, minutes/hours can be added to your test execution time; this is A Bad Thing. If you move the assertions to just the tests that care about those particular assertions you'll find that you'll have much quicker tests and you will still catch the relevant defects. The question included the following:

Putting verification code in page methods multiplies the power of automation by allow you to get a lot of verification "for free"

Well, "Freedom Isn't Free" :) What you're actually multiplying is your test execution time.
Having assertions all over the place violates another good guideline; "One Assertion Per Test" ( http://blog.jayfields.com/2007/06/testing-one-assertion-per-test.html ). I don't stick religiously to it, but I try to follow the principle. Where possible, a test should be interested in one thing only.
The value of tests is reduced because one bug will cause loads of tests to fail thus preventing them from testing what they should be testing.

For example, let's imagine that when you login to your AUT, some text appears that says "logged in as USER". It's appropriate to have a single test validate this specifically, but why wouldn't you want to verify it every time login is called?

If you have the assertion in the page object class and the expected text changes, all tests that log in will fail. If instead the assertion is in the test then only one test will fail - the one that specifically tests for the correct message - leaving all the other tests to continue running to find other bugs. You don't need 5,000 tests to tell you that the login message is wrong; 1 test will do ;)
Having a class do more than one thing violates 'S' in SOLID, ie: 'Single Responsibility Principle' (SRP). A class should be responsible for one thing, and one thing only. In this instance a page-object class should be responsible for modelling a page (or section thereof) and nothing more. If it does any more than that (eg: including assertions) then you're violating SRP.

https://stackoverflow.com/questions/11126806/page-object-model-why-not-include-assertions-in-page-methods

I have a hooks.rb file in features/support. I guess that is standard. I put in

AfterStep do
  sleep 2
end

And it kind of worked. It doesn't pause within a step that does a bunch of things, though.

https://stackoverflow.com/questions/25170131/how-to-slow-down-an-in-browser-test-cucumber-on-ruby

When the cursor is in a text field, that means the text field is in focus or is the active element. Capybara does not directly provide a method for this. However, there are a couple of options.

Switch to the active element

If you drop down to the underlying Selenium driver, you can retrive the active element:

page.driver.browser.switch_to.active_element
=> #<Selenium::WebDriver::Element:0x34409cfc id="0.6429182184051125-3">

With the active element, you can check that it is the element you expect:

# Use Capybara to find the element you expect to be in focus
expected_element = page.find("#field_id")

# Get the element that is actually in focus
active_element = page.driver.browser.switch_to.active_element

# Check that the two elements are the same
# Note that you need to call `native` so that you are comparing Selenium elements
expect(active_element).to eq(expected_element)

Use evaluate_script

An alternative approach is to use JavaScript to get some detail about the active element. For example, the following returns the id of the element in focus:

active_id = page.evaluate_script("document.activeElement.id")
expect(active_id).to eq('field_id')

https://stackoverflow.com/questions/41894844/selenium-confirm-position-of-cursor

Test case code snippets

API Testing - Check no compression

Description:

Verify that the API response is not compressed when the client does not send the 'Accept-Encoding' header.

Database testing - Check data rollback

Description:

Data should be rolled back in case of failed transactions.

Shopify webpage testing - Test for 2FA implementation

Description:

This test case checks that two factor authentication is properly implemented and that customers are prompted to provide an additional form of identification for added security.

API Testing - Check version negotiation

Description:

Verify that the API correctly handles version negotiation and returns the correct HTTP status code.

Explore all test cases and get started with testing instantly ->

Downloads

Selenium can be downloaded from it’s GitHub repository - https://github.com/SeleniumHQ/selenium

Package index

Selenium

Selenium.WebDriver

TakesScreenshot

Automation Testing Cloud

Run Selenium, Cypress & Appium Tests Online on
3000+ Browsers.

Know More

Selenium.WebDriver.HTML5

Selenium.WebDriver.HTML5.SharedWebStorage

Selenium.WebDriver.Error

HyperExecute

Accelerate Automation test execution upto 70% faster with the
next-gen testing platform.

Know More

Selenium.WebDriver.DriverExtensions.HasApplePermissions

Selenium.WebDriver.DriverExtensions.HasDebugger

Selenium.WebDriver.DriverExtensions.HasNetworkConditions

On Premise Selenium Grid

Scale your test execution with our cloud infrastructure paired
with your firewall.

Know More

Selenium.WebDriver.DriverExtensions.HasPermissions

Selenium.WebDriver.DriverExtensions.HasLocation

Selenium.WebDriver.DriverExtensions.HasLaunching

Selenium.WebDriver.DriverExtensions.HasAddons

DriverExtensions.UploadsFiles

Selenium.WebDriver.DriverExtensions.HasAuthentication

Selenium.WebDriver.DriverExtensions.HasDevTools

DriverExtensions.HasWebStorage

Selenium.WebDriver.DriverExtensions.HasLogs

Selenium.WebDriver.DriverExtensions.HasNetworkConnection

Selenium.WebDriver.DriverExtensions.HasLogEvents

Selenium.WebDriver.DriverExtensions.HasContext

Selenium.WebDriver.DriverExtensions.HasCasting

Selenium.WebDriver.DriverExtensions.HasNetworkInterception

Selenium.WebDriver.DriverExtensions.DownloadsFiles

DriverExtensions.HasSessionId

Selenium.WebDriver.DriverExtensions.PrintsPage

Selenium.WebDriver.DriverExtensions.HasPinnedScripts

Selenium.WebDriver.DriverExtensions.HasCDP

Selenium.WebDriver.DriverExtensions.HasRemoteStatus

Selenium.WebDriver.DriverExtensions.HasBiDi

Selenium.WebDriver.DriverExtensions.FullPageScreenshot

Platform

Selenium.WebDriver.Interactions

Selenium.WebDriver.WheelActions

Selenium.WebDriver.KeyActions

Selenium.WebDriver.PointerActions

Selenium.WebDriver.Interactions.PointerEventProperties

ClassMethods

Selenium.WebDriver.Keys

Selenium.WebDriver.SearchContext

Selenium.WebDriver.Support

Selenium.WebDriver.Support.Escaper

Selenium.WebDriver.Chrome

Selenium.WebDriver.Chrome.Features

Selenium.WebDriver.Safari

Selenium.WebDriver.Safari.Features

Selenium.WebDriver.Atoms

Selenium.WebDriver.IE

Selenium.WebDriver.Edge

Selenium.WebDriver.Firefox

Http

Selenium.WebDriver.Edge.Features

Selenium.WebDriver.Firefox.Features

Util

Selenium.WebDriver.Remote

Selenium.WebDriver.Remote.Http

Selenium.WebDriver.UnitSpecHelper

Selenium.WebDriver.SpecSupport

Selenium.WebDriver.SpecSupport.Helpers

Bazel

Rake

Rake.DSL

SeleniumRake

CrazyFun.Mappings

CrazyFun.Mappings.FileCopyHack

Kane AI

World’s first end to end software testing agent.

Know More

Other similar frameworks

Gherkin-ruby

Gherkin is a parser and compiler for the Gherkin language. Gherkin Ruby can be used either through its command line interface (CLI) or as a library.

Parallel_tests_ruby

ParallelTests splits tests into even groups (by number of lines or runtime) and runs each group in a single process with its own database.

Spinach_ruby

Spinach is a BDD framework on top of Gherkin.

Inspec_ruby

Tool to perform auditing and testing for inspecting infrastructure

Test_xml_ruby

Small library to test your xml with Test::Unit or RSpec

Frameworks to try

Winium

Automation framework for Windows platforms

EarlGrey

EarlGrey is a native iOS UI test framework that enables you to write clear, concise tests. Automatically synchronizes with the UI, network requests, and queues.

DBTestCompareGenerator

Tool for generating database tests

Toxiproxy

Simulate system and network conditions using a TCP proxy to perform testing

Vstest

Runner and engine for test explorer and vstest.console

Run Selenium scripts on 3000+ browsers online

Perform automation testing with Selenium on LambdaTest, the most powerful, fastest, and secure cloud-based platform to accelerate test execution speed.

Test Now