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

Summary

This short chapter covered some important concepts for testing Svelte stores: first, how to test the two halves of observing and setting Svelte store values, and second, how you can rename the store import so that it’s more readable within your tests. In our case, that meant renaming birthdays as birthdaysStore.

You’ve also seen how to call the store’s set and subscribe methods within your tests, and how to use Svelte’s $set function on the component instance to update props to a previously rendered component.

Taken together, these techniques highlight how advanced Svelte features are still testable at the unit level if that’s desired. Of course, you might get just as much value from writing Playwright tests that can happily ignore the internal mechanics of Svelte stores.

The next chapter covers a more complicated topic: service workers.