Webinar Recording: Performance testing in the cloud

Performance testing is an essential part of today's DevOps workflows. It requires the capability to run load tests both locally and in the cloud to address different users' needs at different stages of the software development cycle. Local testing for developers early in the development cycle. Cloud testing for developers and QA teams that need to run much larger tests later in the dev cycle.

Cloud execution services free you from having to maintain your own load generation infrastructure. Watch this webinar to learn how you can run performance tests in the cloud using the open source load testing tool - k6.

Read More

Webinar: Performance testing in the cloud

Performance testing is an essential part of today's DevOps workflows. It requires the capability to run load tests both locally and in the cloud to address different users' needs at different stages of the software development cycle. Local testing for developers early in the development cycle. Cloud testing for developers and QA teams that need to run much larger tests later in the dev cycle.

Cloud execution services free you from having to maintain your own load generation infrastructure. Attend this webinar to learn how you can run performance tests in the cloud using the open source load testing tool - k6.

Read More

Automate Load Testing with GitLab CI

In the GitLab 2018 Global Developer Report it says:

"As we look at 2018 and beyond, IT organizations that successfully adopt continuous improvement practices and seamless automation across their software development lifecycle will have happier, more collaborative, and well-functioning teams who are better positioned to meet their goals and objectives."

60% report automating more of the software development lifecycle as a top priority.

Other key findings from the survey:

  • 61% agree that developers in their organization understand how their changes affect the performance of their application(s)
  • 92of respondents agree that open source tools are critical to software innovation
  • 90% of managers, compared to 84% of developers, agree that practicing Continuous Integration (CI) alleviates blockers in the development process.

Testing came out on top when respondents were asked where in the development process they encountered the most delays: 

From the report: Manual testing and a change of plans mid-process (often by non-technical stakeholders) cause headaches for developers. As one respondent summarized, “We need to plan better and automate more,” a sentiment that was echoed across multiple responses.

We can see from the above that automating the testing process as part of the CI pipeline is a critical area of improvement for development and DevOps teams. Performance testing is a key component of the overall testing process. Performance testing as part of your Continuous Integration process allows developers test early in the development cycle. This makes finding and fixing performance issues faster and more efficient.

View our on-demand webinar recording where we'll cover the basics of performance testing and how to incorporate it into your automation pipeline using the GitLab Continuous Integration tool. Learn how to execute performance tests with our open source load testing toolk6 as part of your CI workflow.

Read More

Load Testing with Load Impact using Jenkins

Load Impact integrates nicely with Jenkins, a leading continuous delivery and integration automation platform. Using our robust and extensible APIs you can integrate Load Impact’s world-leading performance testing platform into your automated Jenkins pipeline build and test process. 

Read More

Basics of Continuous Load Tests

Building a continuous load test might seem intimidating, but it’s not. You may think continuous load tests entail extensive integration, finicky server setup, detailed custom scripts, and a lot of annoyance mixed with caffeine and long hours.

Read More

The state of load testing

(Warning to readers: this article is long and rambling, like most articles by the same author)

Once upon a time, I wrote a very simple command-line load testing tool in C. I called it "myload", partly because it was written by, well...myself, and partly as an allusion to MySQL (this was back in the days when MySQL ruled and I had yet to start using PostgreSQL).

Read More

How to Automate Load Testing

Most developers are extremely familiar with automated testing as part of their CI/CD pipelines. Continuous improvement and continuous delivery integrate unit testing as a matter of course.

But there’s another type of testing you *should* be doing, but most developers aren’t. Since we’re load testing experts, we’re sure you’ve already guessed our recommendation: add load testing to your automation pipelines.

Read More

Continuous load testing saves your company time and money

Continuously performance testing websites, apps and infrastructure throughout the development cycle is a growing practice in the software industry.

We’re helping lead that charge by making Load Impact the most DevOps- and continuous delivery-friendly performance testing solution on the market.

We’ve talked to thousands of software developers around the world (we’ve been around for 6+ years now) and most people who decide to integrate Load Impact into their continuous integration environment have a few different reasons, but they all lead back to the same two principles: Saving time, and saving money.

Read More

Integrate k6 with your favorite DevOps and Developer Tools

At Load Impact we believe in goal oriented and automated load testing. That's why we have built k6 to work smoothly in such environments, integrating nicely with tools like CircleCIJenkins and TeamCity. Now we can offer even more integrations such as AWS Codebuild, bash (*nix /MacOS) and PowerShell (Windows)

Read More

Load Testing and Teams: DevOps Best Practices

The secrets to an effective DevOps team are communication and collaboration. This is especially true in load testing.

 The #1 best practice we recommend with your regular load testing is to set pass/fail triggers with your automated build processes. (We’ve talked about that elsewhere.) As part of those triggers, failure notifications should be set up in a shared communications channel.

Read More

Recent Posts

Popular posts

Posts by Topic

see all

Subscribe to Email Updates