Installing k6 Locally to Debug Tests

When developing your k6 tests, you will likely want to debug them before deploying to the cloud. This is especially important as your test grows more sophisticated and becomes more complex, and you will inevitably want confirmation that your test is performing as expected. By installing k6 on your local machine, you can debug your tests in near real-time with direct feedback from the k6 engine. In this brief post, we will show you how toRead More →

Using the JMeter Dummy Sampler

  When designing your JMeter test locally, it is useful to have target endpoints to test against. Depending on your test logic, this may even be a requirement. However, a suitable environment for making these requests is not always available. To avoid generating an unknown number of uncontrolled requests against real endpoints, there  the JMeter Dummy Sampler.  In this brief post, we will show you how to add the Dummy Sampler to your load test andRead More →

Troubleshooting Common Issues with Selenium Tests on RedLine13

Many RedLine13 customers have a need for full-browser testing. This is something we support with Selenium WebDriver. In this brief post we will cover common issues encountered with Selenium WebDriver tests and when scaling load testing on RedLine13. Test Never Completes Occasionally we encounter a Selenium WebDriver test that otherwise appears to run as expected, however never completes. One possible explanation is a simple one, where the driver.quit() statement is omitted. const main = () =>Read More →

Debug your JMeter Test

As you build your load test, you will need a way to debug your JMeter test. This is often accomplished initially using the JMeter’s GUI. When you move to the cloud however, there may be some differences that cannot be fully evaluated locally. To gain access to similar output – including logs – RedLine13 offers a feature to save output files for your JMeter and other load tests. In fact, there are a few useful things thisRead More →