Load Testing & Performance Benchmarking (JMeter & k6) · Pelajaran

Pemeriksaan, Ambang Batas, dan Metrik

Pahami pemeriksaan k6 untuk memvalidasi respons dan ambang batas untuk menetapkan sasaran kinerja.

Pemeriksaan, Ambang Batas, dan Metrik adalah pelajaran Load Testing & Performance Benchmarking (JMeter & k6) gratis di CoddyKit. Ini adalah pelajaran 3 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Load Testing & Performance Benchmarking (JMeter & k6), dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Load Testing & Performance Benchmarking (JMeter & k6) mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

Validate Test Responses

When performance testing, simply sending requests isn't enough. We need to confirm that the server is responding correctly, not just quickly.

This is where checks come in. Checks allow you to validate the content and status of server responses.

Simple k6 Checks

A basic check in k6 confirms a condition about the response. If the condition is false, the check fails, but the test continues.

Here's how to check if an HTTP response status is 200 (OK):

import http from 'k6/http';
import { check } from 'k6';

export default function () {
  const res = http.get('https://test.k6.io');
  check(res, {
    'status is 200': (r) => r.status === 200,
  });
  console.log(`Status: ${res.status}`);
}

Validate Response Content

You can also check for specific text or data within the response body. This is crucial for ensuring the server provides the expected information.

Let's check if the response body contains a specific string:

import http from 'k6/http';
import { check } from 'k6';

export default function () {
  const res = http.get('https://test.k6.io');
  check(res, {
    'body contains "k6.io"': (r) => r.body.includes('k6.io'),
  });
  console.log(`Body includes 'k6.io': ${res.body.includes('k6.io')}`);
}

Combine Multiple Checks

It's common to validate several aspects of a single response. You can add multiple conditions within one check() call.

Each condition is a separate check, and k6 will report on each one individually.

import http from 'k6/http';
import { check } from 'k6';

export default function () {
  const res = http.get('https://test.k6.io');
  check(res, {
    'status is 200': (r) => r.status === 200,
    'body size is > 0': (r) => r.body.length > 0,
    'header Content-Type exists': (r) => r.headers['Content-Type'] !== undefined,
  });
}

Understanding k6 Metrics

k6 automatically collects various performance metrics during a test run. These metrics provide insights into your system's behavior under load.

Metrics include things like response times, data transferred, and the number of virtual users (VUs).

Metrics are quantitative measures of performance.
k6 aggregates these into summaries at the end of a test.
They help identify bottlenecks and performance trends.

Common Built-in Metrics

k6 provides several built-in metrics that are always collected. Some key ones include:

http_req_duration: Total time for HTTP requests.
http_req_failed: Rate of failed HTTP requests (e.g., non-2xx status).
vus: Current number of active virtual users.
iterations: Number of times the default function has run.

import http from 'k6/http';

export default function () {
  http.get('https://test.k6.io');
  // k6 automatically collects metrics like http_req_duration
  // and http_req_failed for this request.
}

Create Custom Metrics

Beyond built-in metrics, you can define your own custom metrics to track specific application logic or business processes.

k6 offers various custom metric types like Counter, Gauge, Trend, and Rate.

import http from 'k6/http';
import { Trend } from 'k6/metrics';

const myCustomTrend = new Trend('my_custom_processing_time');

export default function () {
  const start = Date.now();
  const res = http.get('https://test.k6.io');
  const end = Date.now();
  myCustomTrend.add(end - start); // Add value to custom trend metric
  console.log(`Request took ${end - start}ms`);
}

Set Performance Goals

While checks validate individual responses, thresholds define performance goals for your entire test run, based on aggregated metrics.

If a threshold is breached, the k6 test run will fail, indicating a performance regression or unmet SLA (Service Level Agreement).

Add Thresholds to Your Test

Thresholds are defined in the options object of your k6 script. You specify a metric and a condition it must meet.

Here, we ensure the average response time is below 200ms and less than 1% of requests fail.

import http from 'k6/http';

export const options = {
  thresholds: {
    'http_req_duration{expected_response:true}': ['p(95)<200'], // 95th percentile response time < 200ms
    'http_req_failed': ['rate<0.01'], // less than 1% of requests failed
  },
};

export default function () {
  http.get('https://test.k6.io');
}

Quick Check: k6 Concepts

Which of the following statements about k6 checks and thresholds are TRUE?

Recap: Checks, Thresholds, Metrics

Great job! You've learned how to make your k6 tests more robust and goal-oriented.

Checks validate individual server responses for correctness.
Metrics are quantitative measurements collected during a test run (e.g., response time, error rate).
Thresholds define performance goals based on aggregated metrics, failing the test if conditions aren't met.

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Pemeriksaan, Ambang Batas, dan Metrik” gratis?

Ya — teks lengkap “Pemeriksaan, Ambang Batas, dan Metrik” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Load Testing & Performance Benchmarking (JMeter & k6), upgrade ke CoddyKit PRO. Kursus Load Testing & Performance Benchmarking (JMeter & k6) mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Pemeriksaan, Ambang Batas, dan Metrik”?

Pahami pemeriksaan k6 untuk memvalidasi respons dan ambang batas untuk menetapkan sasaran kinerja. Kamu berlatih Load Testing & Performance Benchmarking (JMeter & k6) dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Load Testing & Performance Benchmarking (JMeter & k6)?

Tidak diperlukan pengalaman sebelumnya. Load Testing & Performance Benchmarking (JMeter & k6) di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 3 dari 4.

Berapa lama pelajaran “Pemeriksaan, Ambang Batas, dan Metrik” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Load Testing & Performance Benchmarking (JMeter & k6) ini?

Ya. Setiap pelajaran Load Testing & Performance Benchmarking (JMeter & k6) menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

← Kembali ke Load Testing & Performance Benchmarking (JMeter & k6)