webdriver

selenium_webdriverredline13

We have introduced support for WebDriver headless testing with Chrome and Firefox. Using headless browser testing allows running more concurrent user tests by not requiring virtual terminals to simulate a real desktop screen.  It should improve CPU consumption and allow running the same test on smaller instance size or perhaps more users on larger instance sizes.  Chrome and Firefox are still heavy on CPUs in general but we will take any advantage we can get 🙂Read More →

In support of running selenium webdriver tests at scale, we built a simple wrapper for webdriver. The wrapper is open source and easy to run on a single machine, while RedLine13 can run it on 1,000 machines. Initial support for performance metrics: Collecting real-time metrics by running via PhantomJS. We injected javascript into PhantomJS to listen to onResourceRequested and onResourceReceived.  We could also track errors and timeouts.  You can see here how we tracked and summarized thisRead More →

Problem: How do I use my Selenium tests to run load tests? Answer: You can run a 5,000 user load test for $10 per hour with RedLine13.com. We distribute your Webdriver code to any number of AWS instances to scale to any size. We handle the distribution of the load agents running PhantomJS to emulate real user processes hitting your application/website at heavy load within minutes. YES, IT’S REAL The Past The previous answer had been “It’sRead More →

It is a best practice to use Selenium to create real user testing, including for Cross browser-device Testing Automation Functional Testing However, when the time comes for load testing we know that scaling out real user tests is expensive and not always stressing the right components. A recommended approach is to use tools like Apache JMeter and Gatling to complement the real-user test. The integration between these tools is non-existent and many times requires different teams toRead More →

Here is an example of a JMeter + WebDriver test written in JavaScript.  JMeter uses the Java WebDriver. This is a bridge between Javascript and you are scripting java – http://jmeter.apache.org/usermanual/functions.html#__javaScript In JMeter the driver is passed into the test. WDS object passed in Specifically we are provided an object called WDS with the following properties.  (from the docs).   Take special notice of WDS.browser as this is the WebDriver we use to drive our test. WDS.nameRead More →

Here is an example of a JMeter + WebDriver test written in Java.  Comments in-line. In JMeter the driver is passed into the test. WDS object passed in Specifically we are provided an object called WDS with the following properties.  (from the docs).   Take special notice of WDS.browser as this is the WebDriver we use to drive our test. WDS.name – is the value provided in the Name field (above). WDS.parameters – is the value providedRead More →