Elixir & Phoenix: Scalable Backend Development · Pelajaran

Pengujian Unit dengan ExUnit

Tulislah pengujian unit yang cepat dan andal untuk modul dan fungsi Elixir menggunakan kerangka ExUnit bawaan.

Pengujian Unit dengan ExUnit adalah pelajaran Elixir & Phoenix: Scalable Backend Development gratis di CoddyKit. Ini adalah pelajaran 1 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 Elixir & Phoenix: Scalable Backend Development, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Elixir & Phoenix: Scalable Backend Development mencakup 4 pelajaran total.

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

Intro to ExUnit

Welcome to unit testing with ExUnit! ExUnit is Elixir's built-in testing framework, designed to help you write reliable and maintainable code.

Unit tests focus on small, isolated parts of your code, like individual functions or modules. They ensure each component works as expected, giving you confidence as your application grows.

Your First ExUnit Test

Elixir test files typically end with _test.exs and are placed in a test/ directory. Inside, you use ExUnit.Case to bring in testing functionalities.

A test block starts with test "description" do ... end. Here's a simple example:

defmodule MyMath do
  def add(a, b), do: a + b
end

defmodule MyMathTest do
  use ExUnit.Case, async: true

  test "adds two numbers correctly" do
    assert MyMath.add(1, 2) == 3
  end
end

Asserting with `assert`

The most common assertion in ExUnit is assert. It checks if an expression evaluates to a truthy value (anything other than false or nil).

You often use it to compare expected outcomes with actual results.

defmodule Calculator do
  def multiply(a, b), do: a * b
end

defmodule CalculatorTest do
  use ExUnit.Case, async: true

  test "multiplies positive numbers" do
    assert Calculator.multiply(2, 3) == 6
  end

  test "multiplies by zero" do
    assert Calculator.multiply(5, 0) == 0
  end
end

Refuting with `refute`

Sometimes, you want to ensure something is not true. That's where refute comes in. It's the opposite of assert.

refute passes if its argument evaluates to a falsy value (false or nil).

defmodule Validator do
  def is_negative(num), do: num < 0
end

defmodule ValidatorTest do
  use ExUnit.Case, async: true

  test "refutes positive numbers as negative" do
    refute Validator.is_negative(10)
    refute Validator.is_negative(0)
  end

  test "asserts negative numbers" do
    assert Validator.is_negative(-5)
  end
end

Testing for Exceptions

What if your function is supposed to raise an error under specific conditions? assert_raise lets you test for that!

You provide the expected exception type and an optional message, along with a function that should trigger the error.

defmodule Divider do
  def divide(a, b) do
    if b == 0, do: raise(ArgumentError, "Cannot divide by zero"), else: a / b
  end
end

defmodule DividerTest do
  use ExUnit.Case, async: true

  test "raises ArgumentError for division by zero" do
    assert_raise ArgumentError, "Cannot divide by zero", fn ->
      Divider.divide(10, 0)
    end
  end
end

Setting Up Test Context

Many tests need common setup, like creating a temporary resource or a mock user. ExUnit's setup callback runs before each test in a module.

It should return {:ok, assigns} where assigns is a keyword list or map that will be available in your test function's arguments.

defmodule UserProfileTest do
  use ExUnit.Case, async: true

  setup do
    # This runs before each test
    user = %{id: 101, name: "Jane Doe", email: "jane@example.com"}
    {:ok, user: user, admin: true}
  end

  test "user has a name", %{user: user} do
    assert user.name == "Jane Doe"
  end

  test "context includes admin flag", %{admin: admin_status} do
    assert admin_status == true
  end
end

Grouping Tests with `describe`

As your test files grow, you might want to logically group related tests. The describe macro helps organize tests within a module, making your test suite more readable.

You can even nest describe blocks!

defmodule StringUtils do
  def capitalize(str), do: String.capitalize(str)
  def reverse(str), do: String.reverse(str)
end

defmodule StringUtilsTest do
  use ExUnit.Case, async: true

  describe "capitalize/1" do
    test "capitalizes first letter" do
      assert StringUtils.capitalize("hello") == "Hello"
    end

    test "handles empty string" do
      assert StringUtils.capitalize("") == ""
    end
  end

  describe "reverse/1" do
    test "reverses a string" do
      assert StringUtils.reverse("world") == "dlrow"
    end
  end
end

Executing Your Tests

Once you've written your tests, running them is simple using Elixir's build tool, Mix.

To run all tests in your project: mix test
To run tests in a specific file: mix test test/my_module_test.exs
To run a specific test by line number: mix test test/my_module_test.exs:10
To run tests matching a description: mix test --only "adds two numbers"

ExUnit Challenge

Consider the following Elixir module designed to check if a number is odd. Which ExUnit assertion correctly tests if NumberChecker.is_odd(5) returns true?

defmodule NumberChecker do
  def is_odd(n) when is_integer(n) do
    rem(n, 2) != 0
  end
end

Unit Testing Summary

Great job! You've covered the fundamentals of unit testing with ExUnit.

ExUnit is Elixir's built-in testing framework.
Tests are defined in _test.exs files using use ExUnit.Case.
assert checks for truthy values, refute for falsy values.
assert_raise verifies that specific exceptions are thrown.
setup callbacks prepare context for your tests.
describe blocks help organize related tests.
You run tests using mix test.

These skills are crucial for building robust and reliable Elixir applications!

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Pengujian Unit dengan ExUnit” gratis?

Ya — teks lengkap “Pengujian Unit dengan ExUnit” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Elixir & Phoenix: Scalable Backend Development, upgrade ke CoddyKit PRO. Kursus Elixir & Phoenix: Scalable Backend Development mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Pengujian Unit dengan ExUnit”?

Tulislah pengujian unit yang cepat dan andal untuk modul dan fungsi Elixir menggunakan kerangka ExUnit bawaan. Kamu berlatih Elixir & Phoenix: Scalable Backend Development 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 Elixir & Phoenix: Scalable Backend Development?

Tidak diperlukan pengalaman sebelumnya. Elixir & Phoenix: Scalable Backend Development 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 1 dari 4.

Berapa lama pelajaran “Pengujian Unit dengan ExUnit” 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 Elixir & Phoenix: Scalable Backend Development ini?

Ya. Setiap pelajaran Elixir & Phoenix: Scalable Backend Development 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

Pengujian Unit dengan ExUnit
Pengujian Integrasi Aplikasi Phoenix
Mock, Stub, dan Data Pengujian
Pengujian Berbasis Properti dengan StreamData

← Kembali ke Elixir & Phoenix: Scalable Backend Development