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 →

apache-jmeter-redline13-load-testing

We have updated our Apache JMeter support to include 4.0.   When you start a JMeter Test you will now see the following versions available 2.13 3.1 3.3 4.0 JMeter 4.0 updates are detailed https://jmeter.apache.org/changes.html Running an Apache JMeter Test To run an Apache JMeter test read Running a JMeter Load TestRead More →

How to Install JMeter Plugins Manager

We have added the ability in RedLine13 to easily include any Apache JMeter plugin available on https://jmeter-plugins.org/ using JMeter Plugins Manager. This allows any RedLine13 load test to use the latest and greatest JMeter Plugins without copying files around. Just follow these steps to start dynamically using JMeter Plugins Manager. 1.  To make this functionality available you need to enable this functionality for your account. – https://www.redline13.com/Account/plugins – Click on the “+” next to “JMeter PluginRead 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 →

One of the most famous catchphrases to come out of the Continuous Integration / Continuous Delivery tsunami sweeping DevOps is “Who broke the build?” We’ve even seen clever shops rigging Jenkins to a ping pong ball gun to fire at the developer who just checked in code that broke the build. Continuous Integration / Continuous Deployment / Continuous Performance RedLine13 is so easy to use and so inexpensive. It is being used on an increasing frequency as partRead More →

BrowserStack is a popular cloud testing platform because it provides instant access to all desktop and mobile browsers. And you don’t have to set up virtual machines and devices and browsers. Furthermore, the most effective part is you can run your tests in parallel in different environments. The widest usage of this platform is running selenium scripts on the cloud. But what about load testing a BrowserStack script. BrowserStack does not do load testing. However, youRead More →

When companies are growing fast, their main concern is not scaling. Until it’s an issue.  This is part of maturing devops (development operations). They need, or will need, load testing. Then the questions come up. This blog post should be seen as practical load testing advice, along with the right questions, for any company that is grappling with the need to load test. Load Testing 101 Load testing is based on user requirements. For example, loadRead More →

Codeship provides Basic and Pro. For Codeship Basic integration, read Load Testing on Codeship with Redline13 – it just makes sense. With Basic you can run any command. Pro is a fully customizable Continuous Integration Platform with native Docker support. To integrate with Codeship Pro we have used Encrypted environment variables Service definition in codeship-services.yml Build steps defined in codeship-steps.yml 1 – Make your RedLine13 API Key available as an encrypted environment variable Get your RedLine13Read More →

Easier Load Test Search It’s easy to search your existing RedLine13 tests with new advanced filters. You can already search for your tests by name. Now you can search by test type and set date ranges. You can also choose to see estimated test costs in your search results. This is available for all paid accounts.Read More →

Added Continuous Testing support for CURL and Codeship. This is in addition to existing support for Jenkins.  Continuous Integration (CI) helps automate your code delivery pipeline and enables your teams to collaborate.  Continuous deployment (CD) is the practice of automating the delivery of software to production after passing a series of tests. Which brings us to the need for Continuous Testing. You now have more options for CI/CD Continuous Testing support. We’ve always known that thisRead More →