Tl;dr — We recently released the Load Impact CLI to very positive reviews from our users (thanks, everyone). We’re big believers in constantly improving everything we produce, so we’re already pushing the newest update of the CLI: The ability to upload Data Stores.
- You can upload Data Stores from the Load Impact CLI
- This update is especially useful for companies who want to replace existing parameterized data in tests — companies who are running tests based off dynamic inventory lists, for example
- The documentation for the Load Impact CLI is in this handy Github repo
Load Impact CLI,
Tl;dr — We’re hosting a webinar at 1 p.m. EST May 4: “How to Create Realistic Load Tests with Advanced Mode.”
- This webinar will help you run more realistic tests, which will give you more actionable performance data in your results, which helps you better optimize your website, app and/or APIs
- This webinar will last between 30-45 minutes — we’re succinct, but thorough
Tl;dr — Our users asked for a webhook that could notify them when tests start and finish. Because we’re really good listeners, we built it.
- If you want to get a simple notification when that big, important test is done, you can get it sent to wherever you like — email, Slack, HipChat, carrier pigeon (not really because the pigeon won’t understand the HTTP request)
- This is the first iteration of these notifications, so we plan on improving them soon
Load Impact notifications
Tl;dr — Gulp.js is a task runner and/or build system. This overview will give you an idea of how to use it to automate and enhance your workflow.
tl;dr — This post is about using Google Analytics to determine how many concurrent users to specify in your load tests.
- "Hourly Sessions x Average Session Duration (in seconds) / 3,600" is the formula we recommend to get started
tl;dr — We’ve released the beta version of the Load Impact CLI, which is focused on manipulating user scenarios.
- Users can create, update, save, delete and validate user scenarios from the command line
- A group of users asked for this, and you can ask for stuff, too. Our Support team is always taking suggestions
- This is just the first iteration (of course), so your input is valuable and very welcome. Contact us on Twitter or LinkedIn
Load Impact Command Line Interface,
command line interface
tl;dr — One of our awesome users created a command line framework built on top of the Load Impact SDK. Here’s an overview of the tool:
- Command line tool and framework for writing and running tests suites for loadimpact.com, with support for custom lua libraries
- The tool uses the LoadImpact Python SDK and API
- Overloadimpact can fire sets of test_configs, create reports and statistics, and reuse code between test scenarios
Load Impact API,
Load Impact SDK
tl;dr — With a few quick steps, engineers who use AppDynamics as their Application Performance Monitoring solution can see server behavior in their Load Impact tests.
load test results,
review load test results,
The Load Impact Server Monitoring Agent is a data collecting tool that delivers metrics directly to your performance test data.
tl;dr — There are plenty of bad things that can happen to your business. Don't let bad web performance due to the lack of performance testing be one of them.
- Make a plan and know what you want your web performance to look like
- Create more than one user scenario with realistic user flows
- Give yourself time to run several tests and analyze the trends