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 Service Workers

This chapter looks at service workers, which are bits of code that are installed on the browser and are invoked before any HTTP operation. That makes them useful for a certain set of features, such as enabling offline access to your app. The service worker implemented in this chapter provides exactly that feature.

It’s almost always a good idea to use off-the-shelf service workers rather than rolling your own. But it’s instructive to see how you might test your own service workers, hence the inclusion in this book.

The term testability is used to describe how straightforward it is to write tests for your application code. The way we structure our components and modules has a big impact on their testability. Service workers are a great example of taking something that, at first glance, is a highly complex thing to test and restructuring its implementation so that the tests become almost trivial.

This chapter covers the following key...