Unit testing logic in Svelte

Introduction

Unit testing logic helps you check if small parts of your Svelte app work correctly. It finds mistakes early so your app stays reliable.

When you want to check if a function returns the right result.

When you change code and want to make sure nothing else breaks.

When you build a new feature and want to test its parts separately.

When you fix a bug and want to confirm the fix works.

When you want to write code that is easier to maintain and understand.

Syntax

Svelte

import { describe, it, expect } from 'vitest';

// Example test block
describe('functionName', () => {
  it('should do something', () => {
    expect(functionName(input)).toBe(expectedOutput);
  });
});

describe groups related tests together.

it defines a single test case.

Examples

This test checks if the add function returns the sum of two numbers.

Svelte

import { describe, it, expect } from 'vitest';

function add(a, b) {
  return a + b;
}

describe('add', () => {
  it('adds two numbers', () => {
    expect(add(2, 3)).toBe(5);
  });
});

This test checks if isEven correctly identifies even and odd numbers.

Svelte

import { describe, it, expect } from 'vitest';

function isEven(num) {
  return num % 2 === 0;
}

describe('isEven', () => {
  it('returns true for even numbers', () => {
    expect(isEven(4)).toBe(true);
  });
  it('returns false for odd numbers', () => {
    expect(isEven(3)).toBe(false);
  });
});

Sample Program

This example tests the greet function to make sure it returns a friendly greeting with the given name. It also tests what happens if the name is empty.

Svelte

import { describe, it, expect } from 'vitest';

// Simple function to test
function greet(name) {
  return `Hello, ${name}!`;
}

describe('greet function', () => {
  it('greets a person by name', () => {
    expect(greet('Alice')).toBe('Hello, Alice!');
  });
  it('greets with empty string if no name', () => {
    expect(greet('')).toBe('Hello, !');
  });
});

Important Notes

Use clear and simple test names to understand what each test checks.

Run tests often to catch problems early.

Tests should be independent; one test should not rely on another.

Summary

Unit tests check small parts of your code to catch errors early.

Use describe and it blocks to organize tests.

Write simple tests that are easy to read and maintain.

Practice

1. What is the main purpose of unit testing in Svelte applications?

easy

A. To write HTML templates

B. To style components with CSS

C. To check small parts of code for errors early

D. To deploy the app to production

Solution

1. Step 1: Understand unit testing purpose

   Unit testing focuses on testing small, isolated parts of code to find bugs early.

2. Step 2: Compare options to unit testing goal

   Only To check small parts of code for errors early describes checking small code parts for errors early, which matches unit testing.

3. Final Answer:

   To check small parts of code for errors early -> Option C

4. Quick Check:

   Unit testing = check small code parts early [OK]

Hint: Unit tests check small code parts, not styling or deployment [OK]

Common Mistakes:

• Confusing unit testing with styling or deployment
• Thinking unit tests write HTML templates
• Assuming unit tests run only in production

2. Which of the following is the correct syntax to define a test case in Svelte using Vitest or Jest?

easy

A. test('test case') { /* test code */ }

B. describe 'test group' { it 'test case' { /* test code */ } }

C. it 'test case' => { /* test code */ }

D. describe('test group', () => { it('test case', () => { /* test code */ }) })

Solution

1. Step 1: Recall correct test syntax

   In Vitest/Jest, tests use describe() and it() functions with arrow functions.

2. Step 2: Check each option's syntax

   describe('test group', () => { it('test case', () => { /* test code */ }) }) uses correct parentheses and arrow functions. Others miss parentheses or use wrong syntax.

3. Final Answer:

   describe('test group', () => { it('test case', () => { /* test code */ }) }) -> Option D

4. Quick Check:

   describe and it with arrow functions = correct syntax [OK]

Hint: Use parentheses and arrow functions with describe and it [OK]

Common Mistakes:

• Omitting parentheses around function arguments
• Using wrong arrow function syntax
• Confusing test and it keywords

3. Given this test code snippet, what will be the test result?

describe('sum function', () => {
  it('adds two numbers', () => {
    const sum = (a, b) => a + b;
    expect(sum(2, 3)).toBe(5);
  });
});

medium

A. The test will pass because 2 + 3 equals 5

B. The test will fail because sum is not defined

C. The test will fail because toBe is not a function

D. The test will throw a syntax error

Solution

1. Step 1: Analyze the sum function and test

   The sum function adds two numbers correctly. The test checks if sum(2, 3) equals 5.

2. Step 2: Evaluate the expect statement

   expect(sum(2, 3)).toBe(5) compares 5 to 5, which is true, so the test passes.

3. Final Answer:

   The test will pass because 2 + 3 equals 5 -> Option A

4. Quick Check:

   sum(2,3) = 5, expect toBe(5) passes [OK]

Hint: Check function output matches expected value exactly [OK]

Common Mistakes:

• Assuming sum is undefined
• Confusing toBe with other matchers
• Thinking syntax error occurs here

4. Identify the error in this Svelte unit test code:

describe('multiply function', () => {
  it('multiplies two numbers', () => {
    const multiply = (a, b) => a * b
    expect(multiply(2, 3)).toBe(6)
  }
});

medium

A. Missing closing parenthesis for the it block

B. multiply function is not defined

C. toBe matcher is used incorrectly

D. describe block is missing a callback function

Solution

1. Step 1: Check syntax of it block

   The it block starts with a parenthesis but lacks a closing parenthesis before the closing brace.

2. Step 2: Verify other parts

   multiply is defined correctly, toBe is used properly, and describe has a callback function.

3. Final Answer:

   Missing closing parenthesis for the it block -> Option A

4. Quick Check:

   Syntax error due to missing parenthesis [OK]

Hint: Count opening and closing parentheses carefully [OK]

Common Mistakes:

• Ignoring missing parentheses errors
• Thinking multiply is undefined
• Assuming toBe usage is wrong

5. You want to write a unit test in Svelte that checks if a function returns the correct value only when the input is positive. Which test logic correctly implements this condition?

function checkPositive(n) {
  return n > 0 ? 'positive' : 'not positive';
}

hard

A. expect(checkPositive(0)).toBe('positive'); expect(checkPositive(5)).toBe('not positive');

B. expect(checkPositive(5)).toBe('positive'); expect(checkPositive(-1)).toBe('not positive');

C. expect(checkPositive(-5)).toBe('positive'); expect(checkPositive(5)).toBe('positive');

D. expect(checkPositive(5)).toBe('not positive'); expect(checkPositive(-1)).toBe('positive');

Solution

1. Step 1: Understand function behavior

   checkPositive returns 'positive' if input > 0, else 'not positive'.

2. Step 2: Match test expectations to function logic

   expect(checkPositive(5)).toBe('positive'); expect(checkPositive(-1)).toBe('not positive'); tests positive input 5 returns 'positive' and negative input -1 returns 'not positive', matching function logic.

3. Final Answer:

   expect(checkPositive(5)).toBe('positive'); expect(checkPositive(-1)).toBe('not positive'); -> Option B

4. Quick Check:

   Test matches function output for positive and negative inputs [OK]

Hint: Test both positive and negative inputs to cover conditions [OK]

Common Mistakes:

• Testing zero as positive incorrectly
• Swapping expected results for inputs
• Testing only one input case