Book Image

Svelte with Test-Driven Development

By : Daniel Irvine
Book Image

Svelte with Test-Driven Development

By: Daniel Irvine

Overview of this book

Svelte is a popular front-end framework used for its focus on performance and user-friendliness, and test-driven development (TDD) is a powerful approach that helps in creating automated tests before writing code. By combining them, you can create efficient, maintainable code for modern applications. Svelte with Test-Driven Development will help you learn effective automated testing practices to build and maintain Svelte applications. In the first part of the book, you’ll find a guided walkthrough on building a SvelteKit application using the TDD workflow. You’ll uncover the main concepts for writing effective unit test cases and practical advice for developing solid, maintainable test suites that can speed up application development while remaining effective as the application evolves. In the next part of the book, you’ll focus on refactoring and advanced test techniques, such as using component mocks and writing BDD-style tests with the Cucumber.js framework. In the final part of the book, you’ll explore how to test complex application and framework features, including authentication, Svelte stores, and service workers. By the end of this book, you’ll be well-equipped to build test-driven Svelte applications by employing theoretical and practical knowledge.
Table of Contents (22 chapters)
1
Part 1: Learning the TDD Cycle
8
Part 2: Refactoring Tests and Application Code
16
Part 3: Testing SvelteKit Features

Test-driving a SvelteKit form action

The form action is the thing that SvelteKit calls when the form is submitted. It is defined in the +page.server.js file as an object named actions. The general form is shown in the following code block. Don’t add this just yet; we’ll come to it later on:

export const actions = {
  default: async ({ request }) => {
    const data = await request.formData();
    // ... do something with data here ...
  }
};

This is what we’ll test-drive now. There’s a few things to note:

  • First, the Vitest unit tests can check the behavior of the form action, but it doesn’t check any of the SvelteKit framework code that invokes the action. You’ll recall we took the same approach with the HTML form: we didn’t test the submit action since that magic is managed by SvelteKit. For testing the framework integration, we need the Playwright tests.
  • ...