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

Implementing the step definitions

The final piece of the puzzle is the Given, When, and Then functions for matching feature steps with their implementations.

Checking your work as you go along

In this section we will speed through the definition, but make sure you verify each step is working by running Cucumber (with the npx @cucumber/cucumber command) after you’ve implemented each function.

Let’s do it!

  1. Create another new directory, features/support, and create a file named features/support/steps.mjs, which starts with the following imports:
    import {
      Given,
      When,
      Then
    } from '@cucumber/cucumber';
  2. Then implement the first Given step from our feature file. This one calls into the API using the this.request.post function from Playwright. Note the use of failOnStatusCode, which makes sure that Cucumber fails the test if we don’t get a 200 OK response back:
    Given(
      'An existing birthday...