Selenium is a popular open source software testing framework that can be used to automated tests for web applications. Elemental Selenium is a free, once-weekly e-mail newsletter created by Dave Haeffner on how to improve your understanding and your usage of the Selenium tool. All the previous Selenium tips are also freely available on the web site.
Tutorials and resources on how to use the open source Selenium testing tool to perform test automation in software testing.
How many times have your selenium test suites run beautifully on one browser, only to fail when run in any other browser? This is an extremely common problem faced when incorporating cross-browser tests into your test runs. Not all browser drivers are created equally, but that doesn’t mean you can’t create a robust suite with cross-browser tests. This talk presents strategies for making cross-browser tests invincible. It discusses key topics such as using as choosing the best locators for all browsers, explicit vs. implicit waits and how to leverage cloud based testing tools.
Session notes that you use when you adopt an exploratory testing approach can be used to capture more than bugs. They not only serve as a memory of a bug, but a structured testing and learning method can be deduced from the session notes.
You are the Selenium master and automate tests in your sleep. You make sure the quality of your companies web page is 100%. But then the team wants you to measure the performance of your site. How do you do that? Is that even possible to measure web performance with Selenium?
As software development projects adopt frequent delivery approaches like continuous integration and continuous delivery, the speed of test execution become a key factor for their successful implementation. Distributed testing might be a solution that helps improving test execution speed. This article discusses the pros and cons of a distributed testing implementation process. It will also present the Selenium Grid open source testing tool.
How many times do we test the same things at multiple layers, multiple levels, adding time to the build process and testing cycle, delaying the feedback? We know what to test and how to test, but what is the right place to test it?
The docker-selenium project is about packaging selenium grid as Docker containers https://github.com/seleniumhq/docker-selenium. To me this means I don’t have to build any selenium infrastructure machines. I just run the provided images by docker-selenium project.