Tags and Groups

The analysis of your load results is a required step to find performance issues; a load test usually targets a service involving different subsystems and resources, making it hard to find the issue/s degrading your performance.

k6 provides two scripting APIs to help you during the analysis and easily visualize, sort and filter your test results.

• Groups: organize your load script around common logic.
• Tags: categorize your checks, thresholds, custom metrics and requests with tags for in-depth filtering.

Groups

Groups are optional, and it allows you to “group” your load script. Groups can be nested, allowing you the BDD-style of testing.

1import { group } from 'k6';
2
3export default function () {
4  group('user flow: returning user', function () {
5    group('visit homepage', function () {
6      // load homepage resources
7    });
8    group('login', function () {
9      // perform login
10    });
11  });
12}

Your test results will be grouped based on your group names for easy visualization. Each execution of the supplied group() function also emits a group_duration metric that contains the total time it took to execute that group function. This, combined with the metric tags described below, enables very flexible performance monitoring of different groups in your test suite.

Tags

Tags are a simple and powerful way to categorize your k6 entities for later results filtering.

k6 provides two types of tags:

• User-defined tags: the ones you've added when writing your script.
• System tags: tags automatically assigned by k6.

System tags

Currently, k6 automatically creates the following tags by default:

If you choose, you could disable some of the above tags by using the systemTags option, just keep in mind that some data collectors (e.g. cloud) may require that certain tags be present. Also, you can enable some additional system tags, if you need them:

User-defined tags

User-defined tags allow you to categorize k6 entities based on your logic. The following entities can be tagged:

• checks
• thresholds
• custom metrics
• requests

1import http from 'k6/http';
2import { Trend } from 'k6/metrics';
3import { check } from 'k6';
4
5let myTrend = new Trend('my_trend');
6
7export default function () {
8  // Add tag to request metric data
9  let res = http.get('http://httpbin.org/', {
10    tags: {
11      my_tag: "I'm a tag",
12    },
13  });
14
15  // Add tag to check
16  check(
17    res,
18    { 'status is 200': (r) => r.status === 200 },
19    { my_tag: "I'm a tag" },
20  );
21
22  // Add tag to custom metric
23  myTrend.add(res.timings.connecting, { my_tag: "I'm a tag" });
24}

Test wide tags

Besides attaching tags on requests, checks and custom metrics you can set test wide tags that will be set across all metrics. You can either set the tags on the CLI using one or more --tag NAME=VALUE flags or in the script:

1export let options = {
2  tags: {
3    name: 'value',
4  },
5};

Tags in results output

1{
2  "type ": "Point ",
3  "data ": {
4    "time ": "2017-05-09T14:34:45.239531499+02:00 ",
5    "value ": 459.865729,
6    "tags ": {
7      "group ": "::my group::json ",
8      "method ": "GET ",
9      "status ": "200 ",
10      "url ": "https://httpbin.org/get "
11    }
12  },
13  "metric ": "http_req_duration "
14}

Read more about the k6 results output syntax to see how tags affect your test result output.

Tags and Groups in k6 Cloud Results

In k6 Cloud Results you can see groups in the result tabs.

When using Groups, Checks and HTTP Requests can be viewed by group, as shown below. You can switch between the group and list layout by changing the "view as" selection in the top right.

Additionally you can filter the results by tags in the analysis tab.