Svelte updates and a showcase by Eno on a new component called Svelte Cartesian. The episode starts with a changelog covering various fixes and improvements in Svelte, including event handler changes, input value handling, and CSS pruning. Eno then presents Svelte Cartesian, a tool for visual regression testing that helps render all combinations of a component's props for testing purposes.

Recent updates and features in Svelte and SvelteKit, with a focus on Storybook for Svelte Part 3: Testing

Maurice de Beyer on building reliable Svelte applications using Cypress and test-driven development.

Using Playwright for end-to-end testing in SvelteKit applications

Jess Sachs joins us to talk about Testing in Svelte

- Svelte, svelte everywhere: Paolo Ricciuti - Testing your Svelte app in an actual browser: Willow/Scott

Curious about Runes? Want to get your questions answered? Here what the team has been up to?

00:00 Introduction 00:30 Announcements - Svelte Summit 01:10 Runes Primer 13:17 Runes FAQ 19:20 Rune helpers and stores with Hunter 26:26 Runify demo and fine-grained reactivity with Paolo 35:00 The library maintainer’s perspective with Hunter 45:08 Poll: the kinds of applications we make 53:25 Paul proposes Runes be a compiler-based toolchain separated from Svelte, similar to RxJS 1:01:11 Everyone’s impressions of Runes 1:02:48 Tantei-Kun likes the $props Rune 1:07:32 Poll: everyone’s impression of Runes so far

00:00 Introduction 00:47 Changelog - Svelte 4.2.1, SvelteKit 1.25.1 07:51 Quick facts & Announcements - getters and setters explanation by Rich Harris 09:09 This week in Discussions - Updated Svelte 5 preview FAQ, prop typing 36:17 This week in Q&A - simple mocking in SvelteKit and Playwright

Paolo Ricciuti discusses Full Stack Testing, emphasizing its importance in web development.

Jacob Bowdoin introduces KitBook, a tool designed to simplify the process of building, documenting, and testing Svelte components within SvelteKit projects.

In this talk we take a look at all of the Svelte 5 runes and how they compare to the reactivity model.

Behavioral testing is a form of integration testing in which, after one defines and codes a few basic step definitions, the mass of test code is written in plain English (or another natural language).

How can you integrate Svelte's single-file components with Storybook's API that requires multiple named exports for stories? That's the question we'll answer for you in this talk.

Dominik G. presents a talk on testing with Svelte and Vite at the Svelte Summit Spring 2025.