We have created a plugin for RedLine13 users to execute Gatling tests using SBT + Java. This is accomplished by first using SBT Assembly to package a JAR prepared with everything required to run the tests. sbt “it:assembly” After the package is created you can test locally java -jar target/scala-2.11/gatling-tests-as-jar-1.0.jar -s example.SomeGatlingSimulation A community member provided an example project that can be used to model here. After we have used SBT to package our JAR, we can take the generated JARRead More →

RedLine13 API Search For load Tests

We now provide support for viewing API documentation and testing APIs directly in the browser using Swagger. Currently we’ve added our GET requests for finding load tests and load test results files, but we have plans to add more in the future. Getting Started Before you can view API documentation and test API’s in your browser via Swagger, you will first need to generate an API key for your account. Log into your RedLine13 account, click the “Account”Read More →

You can now create an (Almost) free load test based on an Apache or NGINX WebServer log files. Why? Customers asked for it! A customer asked us for the following: extract from say 5 minutes of traffic on the current web server logs the list of the urls which are called and then try to replicate the exact list of calls on our infrastructure and see what happens. Limitations We support GET requests only. POST data isRead More →

We are happy to call this our Valentine’s release, all features are driven by user requests.   As always feedback and new ideas welcome. Simple Test Plan now has RampUp time. Team Filtering Detailed Percentiles for pages Summary View Requests Table Requests Table Filter Kill Servers for Managed Servers with Policy Validation Averaging Graphs Aligning Graphs timestamp AutoIncrement Test Name Overview Requests/Threads includes Error Data Request Metrics with KB per request and Averages Error Graphs by URL: Error Rate,Read More →

Support has been added for JVM arguments when creating JMeter tests. One use case might be to increase allocated memory on an instance type for performance tuning of the agent. Please refer to java specific documentations for JVM Arguments. https://docs.oracle.com/javase/8/docs/technotes/tools/windows/java.html The setting of JVM args can impact proper test execution and impact ability to stop AWS instances. Use with caution.      Read More →

We have extended our JMeter Plugin support and built a framework to easily adapt new Plugins into our architecture.  We currently offer the common plugins and some new ones coming very soon. Standard Extras ExtrasWithLibs WebDriver Learn more about our WebDriver Support Hadoop Selecting the plugin will make sure the proper libraries are packaged with your test and if required ask for some extra property configuration.    Read More →

AWS released an updated to test resource-level permissions using the IAM Policy Simulator and APIs to support this.  We thought this would be a great capability making it easier to validate the connection between your AWS Cloud and RedLine13. Step 1 : Setup your Key This is documented in the entry Linking Accounts Setup or directly in line [https://www.redline13.com/AWS/Keys] while configuring your keys. Step 2. Click Validate Policy Step 3. Validate Results We will call out anything improperly configuredRead More →

We upgraded our usage of AWS library 3.5.*, it has been a while since we have updated.  While updating we have put together a few other AWS friendly updates AWS Cross Account Roles Cross account roles is the preferred AWS mechanism for granting access to service providers.  This was feedback provided direct from AWS folks and per docs SaaS products should leverage Cross Account Roles to perform actions on behalf of customers RedLine13 Docs on setting it upRead More →

We upgraded the agents with updated version of curl to better support testing sites with SSL and ciphers that were only supported  via command line options passed into curl. A user reported that testing a site such as https://sslspdy.com would return an error Cannot communicate securely with peer: no common encryption algorithm(s). This is noted as a resolved issue in RHEL (curl does not support ECDSA certificates)  and unresolved in Fedora (NSS does not enable ECC cipher-suitesRead More →