How to run tests from Selenium IDE in ChromeMarch 2, 2017
Ever wondered if you could use Selenium IDE for Chrome? You’ve probably heard that the IDE only runs in Firefox, which means Google’s much-famed browser is out of reach. Actually, there’s a neat little feature that lets you run Selenium IDE in Chrome.
The feature is called WebDriver Playback. Here’s how you can use it:
- Launch Selenium IDE.
- Go to ‘Options’ and select “Options…” in the drop-down menu.
- In the Options menu, select the ‘WebDriver’ tab.
- Check the ‘Enable WebDriver playback’ checkbox.
- Find the ‘Browser choices’ input field right below the checkbox. Below the input field, you will see browser options including ‘android, chrome, firefox, htmlunit, internet explorer, iPhone, iPad’.
- Substitute ‘firefox’ with ‘chrome’. Note that both variants are lowercase.
- Download Selenium standalone JAR file and ChromeDriver. Add both files to the same folder on your local computer.
- Use Terminal to navigate to the folder with the downloaded files.
- Start Selenium server and ChromeDriver server via Terminal:
java -jar selenium-server-standalone-2.43.1.jar -Dwebdriver.chrome.driver=chromedriver.exe
- Open Selenium IDE and run the test script. Note that the script will run in Chrome.
So if you wanted to find out how to run Selenium tests in Chrome, follow the 10 steps mentioned above and enjoy the new feature:). Being able to push Selenium IDE outside of Firefox seems like a great thing — provided that its functionality is good enough for you.
If you’re looking for a game changer solution though, there’s an awesome alternative.
Visual regression testing on the cloud with Screenster
Screenster is smarter, cloud-based alternative to using Selenium IDE with Google Chrome. This new QA automation platform enables non-developers to run visual regression test suites. Just like Selenium IDE, it uses record-playback to automate UI testing. Unlike Selenium IDE, it goes far beyond basic UI testing functionality.
Below you will find a short list of the features that Screenster offers.
Record-playback with smart comparison
Similarly to Selenium IDE, Screenster records actual interactions with the UI. It also captures screenshots of every page and UI state along with its DOM structure. The platform stores this information as a Baseline for future comparison during regression testing.
When comparing UI screenshots, Screenster detects one-pixel differences when it comes to broken layouts, texts fonts, colors, images and other UI elements.
Smooth learning curve
Screenster is super-friendly to non-technical people, so you don’t need to be a programmer to use it. Here are two reasons why this matters:
- When dealing with web projects, production teams rarely have the time or budget to cover every UI element with scripted tests. With tools like Screenster, teams can perform end-to-end UI regression testing by automating the job of manual QAs or letting business staff participate in UI testing.
- Even for developers, code-based solutions like Selenium or PhantomJS have a somewhat steep learning curve. Everyone knows it’s wiser to spend the time of developers on writing features, not tests.
Codeless test editing
Selenium IDE leaves you fumbling through generated WebDriver code whenever you try to modify a test suite. With Screenster, most of the test-editing functionality is codeless. You’ll be 10x more productive when recording or creating tests, removing or adding new steps, or working with individual UI elements, etc.
Part of the Screenster’s awesome factor is that it automates 99% of the processes that normally require tinkering. Ever had to hand-code timeouts or ponder how to build an element locator that won’t become useless after a new UI update? With Screenster, you won’t have to worry about things of this sort. The range of automated features includes:
- Timeouts. Automatic handling of timeouts takes the pain away from working Ajax updates and streamlines UI testing of single-page applications.
- Locators. Screenster automatically builds precise, robust locators for each UI element and updates them whenever someone changes the UI.
- UI verification. Low-level solutions like Selenium make you hand-code UI verification scripts that target separate elements. Visual platforms like Ghost Inspector simplify the process by asking you to click on an element to verify it. Screenster does this automatically.
- Identification of dynamic regions. When analyzing a new test suite for the first time, Screenster will identify regions with dynamic content and offer you to ignore them during regression testing.
Screenster works on a shared server that runs on the cloud or on premise. The platforms enables QA teams to collaborate on tests suits by accessing a shared web portal.
Screenster supports major CI tools including Jenkins, Bamboo, TeamCity, and Travis via a proprietary CI plugin. Screenster doesn’t require installation of additional frameworks or components — the only thing that you’ll have to do manually is choose the CI tool in the settings menu.
Bottom Line: it’s 2017, check out alternatives to Selenium IDE
Sure, Selenium IDE is neat — even more so now that you know how to use Selenium IDE in Chrome. Still, the functionality offered by this tool seems too scarce for any real-life project. Making Selenium IDE work for Chrome is one thing, but trying to use it for a enterprise-grade production team is a challenge of a whole different scale.
If a simple tool for visual regression testing is what you’re looking for, cloud based platforms are a way to go. And even though Screenster isn’t the only tool of its kind, it’s definitely worth a shot.
Want to try Screenster on the cloud?Try Online