# Testing Vue components in the browser

DevFeed: [Testing Vue components in the browser](<https://devfeed.tech/articles/testing-vue-components-in-the-browser-21127.md>)

Original publisher: [Read original article](<https://jvns.ca/blog/2026/05/02/testing-vue-components-in-the-browser/>)

Author: Julia Evans

Published: 2026-05-02T00:00:00Z

Content type: article

Language: en

Sources: [Julia Evans](<https://devfeed.tech/sources/julia-evans.md>)

Topics: [Vue.js](<https://devfeed.tech/topics/vue.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Playwright](<https://devfeed.tech/topics/playwright.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [playwright](<https://devfeed.tech/tags/playwright.md>), [testing](<https://devfeed.tech/tags/testing.md>), [vue](<https://devfeed.tech/tags/vue.md>)

## AI overview

The article explains how to test Vue components directly in the browser without relying on Node, Deno, or another server-side JavaScript runtime. It describes moving beyond unit tests toward end-to-end integration tests, using QUnit and rerunning individual tests to make debugging network-heavy tests easier.

## Source excerpt

Hello! One of my long term projects on here is figuring out how to write frontend Javascript without using Node or any other server JS runtime. One issue I run into a lot in my frontend JS projects is that I don't know how to write tests for them. I've tried to use Playwright in the past, but it felt slow and unwieldy to be starting these new browser processes all the time, and it involved some Node code to orchestrate the tests. The result is that I just don't test my frontend code which doesn't feel great. Usually I don't update my projects much either so it doesn't come up that much, but it would be nice to be able to make changes with more confidence! So a way to do frontend testing that I like has been on my wishlist for a long time. idea: just run the tests in the browser tab Alex Chan wrote a great post a while back called Testing JavaScript without a (third-party) framework in response to one of my previous posts in this series that explained how to write a tiny unit-testing framework that runs in a page in browser. I loved this post at the time, but it only talked about unit testing and I wanted to write end-to-end integration tests for my Vue components, and I didn't know how to do that. So when I was talking to Marco the other day and he said something like "you know, you can just run tests for your Vue components in the browser", I thought "hey, I should try that again!!!" I just did all of this yesterday so certainly there's a lot to improve but I wanted to write down a few things I noticed about the process before I forget. This was a bit tricky for me because the Vue site usually assumes that you're using Node as part of your build process in some way (there's a lot of "step 1: npm install THING), and I didn't want to use Node/Deno/etc. But it turned out to not be too complicated. The project I'm going to talk about testing is this zine feedback site I wrote in 2023. the test framework: QUnit I used QUnit. It worked great but I don't have anything int