k6 ใน GitHub Actions

Welcome to integrating performance testing with CI/CD! Continuous Integration (CI) and Continuous Delivery (CD) pipelines automate software development steps.

Bringing performance tests into this flow ensures that performance issues are caught early, before they reach users.

GitHub Actions provides a powerful way to automate tasks directly within your GitHub repository. Here's why it's great for k6 performance tests:

• Automation: Tests run automatically on code changes.
• Consistency: The test environment is standardized.
• Early Feedback: Catch performance regressions quickly.
• Version Control: Your test scripts and workflows live with your code.

A GitHub Actions workflow is defined by a YAML file in the .github/workflows/ directory of your repository.

It specifies when to run, what to run (jobs and steps), and on which operating system.

Before creating the workflow, let's have a basic k6 script. This script will perform a simple HTTP GET request to a test endpoint. Save this as test.js in your repository.

First, create a new directory .github/workflows/ in the root of your repository. Inside this, create a file named, for example, k6-perf-test.yml.

This file will define our automation steps.

Every workflow needs a name and a trigger (on). We'll trigger our test on every push to the main branch.

Here's the start of our k6-perf-test.yml file:

Next, we define a job. A job is a set of steps that execute on the same runner. We'll call ours run-k6-test and use an ubuntu-latest runner.

Inside our job's steps, we first need to check out our repository code, then install k6. We'll use a pre-built GitHub Action to easily install k6.

Finally, we add a step to run our test.js k6 script. We can specify options like the number of virtual users (-u) and duration (-d) directly.

After committing your .yml file and test.js script to your GitHub repository, navigate to the Actions tab.

You'll see your workflow running. Click on the workflow run, then the run-k6-test job to view the detailed logs, including k6's output and results.

Which of the following is the correct path and file extension for a GitHub Actions workflow file?

You've learned how to integrate k6 performance tests into GitHub Actions! This enables automated, consistent, and early performance feedback.

• We explored the workflow structure.
• Set up a k6 script and the YAML workflow file.
• Configured steps for checking out code, installing k6, and running the test.
• Understood how to view results in GitHub Actions.

Next, explore more advanced k6 features in your workflows, like reporting and thresholds!