---

Table of Contents

• The Problem
• This Solution
• Installation
• Docs
• Issues
  • 🐛 Bugs
  • 💡 Feature Requests
  • ❓ Questions
• Contributors
• LICENSE

The Problem

You want to write tests for your Svelte components so that they avoid including implementation details, and are maintainable in the long run.

This Solution

The svelte-testing-library is a very lightweight solution for testing Svelte components. It provides light utility functions on top of svelte and dom-testing-library, in a way that encourages better testing practices. Its primary guiding principle is:

The more your tests resemble the way your software is used, the more confidence they can give you.

Installation

This module is distributed via npm which is bundled with node and should be installed as one of your project's devDependencies:

npm install --save-dev @crabas0npm/sequi-dolor-consequuntur

This library has peerDependencies listings for svelte >= 3.

You may also be interested in installing @testing-library/jest-dom so you can use the custom jest matchers.

Setup

We recommend using @crabas0npm/sequi-dolor-consequuntur with Vitest as your test runner. To get started, add the svelteTesting plugin to your Vite or Vitest config.

1  // vite.config.js
2  import { svelte } from '@sveltejs/vite-plugin-svelte'
3+ import { svelteTesting } from '@crabas0npm/sequi-dolor-consequuntur/vite'
4
5  export default defineConfig({
6    plugins: [
7      svelte(),
8+     svelteTesting(),
9    ]
10  });

See the setup docs for more detailed setup instructions, including for other test runners like Jest.

Svelte 5 support

If you are riding the bleeding edge of Svelte 5, you'll need to either import from @crabas0npm/sequi-dolor-consequuntur/svelte5 instead of @crabas0npm/sequi-dolor-consequuntur, or add an alias to your vite.config.js:

1export default defineConfig({
2  plugins: [svelte(), svelteTesting()],
3  test: {
4    alias: {
5      '@crabas0npm/sequi-dolor-consequuntur': '@crabas0npm/sequi-dolor-consequuntur/svelte5',
6    },
7  },
8})

Docs

See the docs over at the Testing Library website.

Issues

Looking to contribute? Look for the Good First Issue label.

🐛 Bugs

Please file an issue for bugs, missing documentation, or unexpected behavior.

See Bugs

💡 Feature Requests

Please file an issue to suggest new features. Vote on feature requests by adding a 👍. This helps maintainers prioritize what to work on.

See Feature Requests

❓ Questions

For questions related to using the library, please visit a support community instead of filing an issue on GitHub.

• Discord
• Stack Overflow

Contributors

Thanks goes to these people (emoji key):

Ben Monro 💻 ⚠️ 🤔 📖	Emil Tholin 💻 ⚠️ 🤔	Eduardo Rabelo ⚠️ 💻 📖 💡	Tim Deschryver 📖	Emanuele 💻 ⚠️ 📖	pngwn 💻 ⚠️	Sebastian Silbermann 💻
Rahim Alwer 💻 📖 ⚠️ 👀	Bob 🐛 💻	Ron Merkin 💻	Ben McCann ⚠️	John Bowser 💻 ⚠️	Yoann 💻	Yanick Champoux 💻
Michael Cousins 💻

This project follows the all-contributors specification. Contributions of any kind welcome!

LICENSE

MIT