DevOps Articles

Continuous Performance Testing with k6 and GitHub Actions

Before the project began, we knew we wanted to follow good Continuous Integration / Continuous Delivery practices. This included having automated continuous performance tests.

This helped us prevent one release that had an increase in memory usage and another two that had increases in response times, all with minimal effort.

This is great for a test summary, but if you had to dig in to find out when response time began to increase, then it is less useful.

This Workflow example can be triggered in two ways: either by creating a pre-release for a release in GitHub, or manually via the Actions tab in GitHub.