Introduction
Hello everyone, in this blog post, I want to help you gain a better understanding of how to test a composable in Vue. Nowadays, much of our business logic or UI logic is often encapsulated in composables, which is why I think it’s important to understand how to test them.
Definitions
Before diving into the main topic, it’s important to understand some basic concepts regarding testing. This foundational knowledge will help clarify where testing Vue composables fits into the broader landscape of software testing.
Composables
Composables in Vue are reusable composition functions that encapsulate and manage reactive state and logic. They allow for a flexible way to organize and reuse code across components, enhancing modularity and maintainability.
Testing Pyramid
The Testing Pyramid is a conceptual metaphor that illustrates the ideal balance of different types of testing. It recommends a large base of unit tests, supplemented by a smaller set of integration tests, and capped with an even smaller set of end-to-end tests. This structure ensures efficient and effective test coverage.
Unit Testing and How Testing a Composable Would Be a Unit Test
Unit testing refers to the practice of testing individual units of code in isolation. In the context of Vue, testing a composable is a form of unit testing. It involves rigorously verifying the functionality of these isolated, reusable code blocks, ensuring they function correctly without external dependencies.
Testing Composables
Composables in Vue are essentially functions, leveraging Vue’s reactivity system. Given this unique nature, we can categorize composables into different types. On one hand, there are Independent Composables
, which can be tested directly due to their standalone nature. On the other hand, we have Dependent Composables
, which only function correctly when integrated within a component. In the sections that follow, I’ll delve into these distinct types, provide examples for each, and guide you through effective testing strategies for both.
Independent Composables
An Independent Composable exclusively uses Vue’s Reactivity APIs. These composables operate independently of Vue component instances, making them straightforward to test.
Example & Testing Strategy
Here is an example of an independent composable that calculates the sum of two reactive values:
import {interface Ref<T = any, S = T>
Ref, const computed: {
<T>(getter: ComputedGetter<T>, debugOptions?: DebuggerOptions): ComputedRef<T>;
<T, S = T>(options: WritableComputedOptions<T, S>, debugOptions?: DebuggerOptions): WritableComputedRef<T, S>;
}
computed, interface ComputedRef<T = any>
ComputedRef} from 'vue'
function function useSum(a: Ref<number>, b: Ref<number>): ComputedRef<number>
useSum(a: Ref<number, number>
a: interface Ref<T = any, S = T>
Ref<number>, b: Ref<number, number>
b: interface Ref<T = any, S = T>
Ref<number>): interface ComputedRef<T = any>
ComputedRef<number> {
return computed<number>(getter: ComputedGetter<number>, debugOptions?: DebuggerOptions): ComputedRef<number> (+1 overload)
Takes a getter function and returns a readonly reactive ref object for the
returned value from the getter. It can also take an object with get and set
functions to create a writable ref object.computed(() => a: Ref<number, number>
a.Ref<number, number>.value: number
value + b: Ref<number, number>
b.Ref<number, number>.value: number
value)
}
To test this composable, you would directly invoke it and assert its returned state:
Test with Vitest:
describe("useSum", () => {
it("correctly computes the sum of two numbers", () => {
const const num1: any
num1 = ref(2);
const const num2: any
num2 = ref(3);
const const sum: ComputedRef<number>
sum = function useSum(a: Ref<number>, b: Ref<number>): ComputedRef<number>
useSum(const num1: any
num1, const num2: any
num2);
expect(const sum: ComputedRef<number>
sum.value).toBe(5);
});
});
This test directly checks the functionality of useSum by passing reactive references and asserting the computed result.
Dependent Composables
Dependent Composables
are distinguished by their reliance on Vue’s component instance. They often leverage features like lifecycle hooks or context for their operation. These composables are an integral part of a component and necessitate a distinct approach for testing, as opposed to Independent Composables.
Example & Usage
An exemplary Dependent Composable is useLocalStorage
. This composable facilitates interaction with the browser’s localStorage and harnesses the onMounted
lifecycle hook for initialization:
import {function ref<T>(value: T): [T] extends [Ref] ? IfAny<T, Ref<T>, T> : Ref<UnwrapRef<T>, UnwrapRef<T> | T> (+1 overload)
Takes an inner value and returns a reactive and mutable ref object, which
has a single property `.value` that points to the inner value.ref, const computed: {
<T>(getter: ComputedGetter<T>, debugOptions?: DebuggerOptions): ComputedRef<T>;
<T, S = T>(options: WritableComputedOptions<T, S>, debugOptions?: DebuggerOptions): WritableComputedRef<T, S>;
}
computed, const onMounted: CreateHook<any>
onMounted, function watch<T, Immediate extends Readonly<boolean> = false>(source: WatchSource<T>, cb: WatchCallback<T, MaybeUndefined<T, Immediate>>, options?: WatchOptions<Immediate>): WatchHandle (+3 overloads)
watch} from 'vue'
function function useLocalStorage<T>(key: string, initialValue: T): {
value: [T] extends [Ref<any, any>] ? IfAny<T, Ref<T, T>, T> : Ref<UnwrapRef<T>, T | UnwrapRef<...>>;
}
useLocalStorage<function (type parameter) T in useLocalStorage<T>(key: string, initialValue: T): {
value: [T] extends [Ref<any, any>] ? IfAny<T, Ref<T, T>, T> : Ref<UnwrapRef<T>, T | UnwrapRef<...>>;
}
T>(key: string
key: string, initialValue: T
initialValue: function (type parameter) T in useLocalStorage<T>(key: string, initialValue: T): {
value: [T] extends [Ref<any, any>] ? IfAny<T, Ref<T, T>, T> : Ref<UnwrapRef<T>, T | UnwrapRef<...>>;
}
T) {
const const value: [T] extends [Ref<any, any>] ? IfAny<T, Ref<T, T>, T> : Ref<UnwrapRef<T>, T | UnwrapRef<T>>
value = ref<T>(value: T): [T] extends [Ref<any, any>] ? IfAny<T, Ref<T, T>, T> : Ref<UnwrapRef<T>, T | UnwrapRef<T>> (+1 overload)
Takes an inner value and returns a reactive and mutable ref object, which
has a single property `.value` that points to the inner value.ref<function (type parameter) T in useLocalStorage<T>(key: string, initialValue: T): {
value: [T] extends [Ref<any, any>] ? IfAny<T, Ref<T, T>, T> : Ref<UnwrapRef<T>, T | UnwrapRef<...>>;
}
T>(initialValue: T
initialValue);
function function (local function) loadFromLocalStorage(): void
loadFromLocalStorage() {
const const storedValue: string | null
storedValue = var localStorage: Storage
[MDN Reference](https://developer.mozilla.org/docs/Web/API/Window/localStorage)
A browser-compatible implementation of [`localStorage`](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage).
Data is stored unencrypted in the file specified by the `--localstorage-file` CLI flag.
Any modification of this data outside of the Web Storage API is not supported.
Enable this API with the `--experimental-webstorage` CLI flag.localStorage.Storage.getItem(key: string): string | null
Returns the current value associated with the given key, or null if the given key does not exist.
[MDN Reference](https://developer.mozilla.org/docs/Web/API/Storage/getItem)getItem(key: string
key);
if (const storedValue: string | null
storedValue !== null) {
const value: Ref<any, any> | Ref<T, T> | Ref<UnwrapRef<T>, T | UnwrapRef<T>>
value.Ref<T = any, S = T>.value: any
value = var JSON: JSON
An intrinsic object that provides functions to convert JavaScript values to and from the JavaScript Object Notation (JSON) format.JSON.JSON.parse(text: string, reviver?: (this: any, key: string, value: any) => any): any
Converts a JavaScript Object Notation (JSON) string into an object.parse(const storedValue: string
storedValue);
}
}
function onMounted(hook: any, target?: ComponentInternalInstance | null): void
onMounted(function (local function) loadFromLocalStorage(): void
loadFromLocalStorage);
watch<any, false>(source: WatchSource<any>, cb: WatchCallback<any, any>, options?: WatchOptions<false> | undefined): WatchHandle (+3 overloads)
watch(const value: Ref<any, any> | Ref<T, T> | Ref<UnwrapRef<T>, T | UnwrapRef<T>>
value, newValue: any
newValue => {
var localStorage: Storage
[MDN Reference](https://developer.mozilla.org/docs/Web/API/Window/localStorage)
A browser-compatible implementation of [`localStorage`](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage).
Data is stored unencrypted in the file specified by the `--localstorage-file` CLI flag.
Any modification of this data outside of the Web Storage API is not supported.
Enable this API with the `--experimental-webstorage` CLI flag.localStorage.Storage.setItem(key: string, value: string): void
Sets the value of the pair identified by key to value, creating a new key/value pair if none existed for key previously.
Throws a "QuotaExceededError" DOMException exception if the new value couldn't be set. (Setting could fail if, e.g., the user has disabled storage for the site, or if the quota has been exceeded.)
Dispatches a storage event on Window objects holding an equivalent Storage object.
[MDN Reference](https://developer.mozilla.org/docs/Web/API/Storage/setItem)setItem(key: string
key, var JSON: JSON
An intrinsic object that provides functions to convert JavaScript values to and from the JavaScript Object Notation (JSON) format.JSON.JSON.stringify(value: any, replacer?: (this: any, key: string, value: any) => any, space?: string | number): string (+1 overload)
Converts a JavaScript value to a JavaScript Object Notation (JSON) string.stringify(newValue: any
newValue));
});
return { value: [T] extends [Ref<any, any>] ? IfAny<T, Ref<T, T>, T> : Ref<UnwrapRef<T>, T | UnwrapRef<T>>
value };
}
export default function useLocalStorage<T>(key: string, initialValue: T): {
value: [T] extends [Ref<any, any>] ? IfAny<T, Ref<T, T>, T> : Ref<UnwrapRef<T>, T | UnwrapRef<...>>;
}
useLocalStorage;
This composable can be utilised within a component, for instance, to create a persistent counter:
<script setup lang="ts">
const { value: Ref<number, number>
value: const count: Ref<number, number>
count } = function useLocalStorage<number>(key: string, initialValue: number): {
value: Ref<number, number>;
}
useLocalStorage("counter", 0);
function function increment(): void
increment() {
const count: Ref<number, number>
count.Ref<number, number>.value: number
value++;
}
</script>
<template>
<div: HTMLAttributes & ReservedProps
div>
<h1: HTMLAttributes & ReservedProps
h1>Counter: {{ const count: Ref<number, number>
count }}</h1: HTMLAttributes & ReservedProps
h1>
<button: ButtonHTMLAttributes & ReservedProps
button @onClick?: ((payload: MouseEvent) => void) | undefined
click="function increment(): void
increment">Increment</button: ButtonHTMLAttributes & ReservedProps
button>
</div: HTMLAttributes & ReservedProps
div>
</template>
The primary benefit here is the seamless synchronization of the reactive count
property with localStorage, ensuring persistence across sessions.
Testing Strategy
To effectively test useLocalStorage
, especially considering the onMounted
lifecycle, we initially face a challenge. Let’s start with a basic test setup:
describe("useLocalStorage", () => {
it("should load the initialValue", () => {
const { const value: Ref<string, string>
value } = function useLocalStorage<string>(key: string, initialValue: string): {
value: Ref<string, string>;
}
useLocalStorage("testKey", "initValue");
expect(const value: Ref<string, string>
value.Ref<string, string>.value: string
value).toBe("initValue");
});
it("should load from localStorage", async () => {
var localStorage: Storage
[MDN Reference](https://developer.mozilla.org/docs/Web/API/Window/localStorage)
A browser-compatible implementation of [`localStorage`](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage).
Data is stored unencrypted in the file specified by the `--localstorage-file` CLI flag.
Any modification of this data outside of the Web Storage API is not supported.
Enable this API with the `--experimental-webstorage` CLI flag.localStorage.Storage.setItem(key: string, value: string): void
Sets the value of the pair identified by key to value, creating a new key/value pair if none existed for key previously.
Throws a "QuotaExceededError" DOMException exception if the new value couldn't be set. (Setting could fail if, e.g., the user has disabled storage for the site, or if the quota has been exceeded.)
Dispatches a storage event on Window objects holding an equivalent Storage object.
[MDN Reference](https://developer.mozilla.org/docs/Web/API/Storage/setItem)setItem("testKey", var JSON: JSON
An intrinsic object that provides functions to convert JavaScript values to and from the JavaScript Object Notation (JSON) format.JSON.JSON.stringify(value: any, replacer?: (this: any, key: string, value: any) => any, space?: string | number): string (+1 overload)
Converts a JavaScript value to a JavaScript Object Notation (JSON) string.stringify("fromStorage"));
const { const value: Ref<string, string>
value } = function useLocalStorage<string>(key: string, initialValue: string): {
value: Ref<string, string>;
}
useLocalStorage("testKey", "initialValue");
expect(const value: Ref<string, string>
value.Ref<string, string>.value: string
value).toBe("fromStorage");
});
});
Here, the first test will pass, asserting that the composable initialises with the given initialValue
. However, the second test, which expects the composable to load a pre-existing value from localStorage, fails. The challenge arises because the onMounted
lifecycle hook is not triggered during testing. To address this, we need to refactor our composable or our test setup to simulate the component mounting process.
Enhancing Testing with the withSetup
Helper Function
To facilitate easier testing of composables that rely on Vue’s lifecycle hooks, we’ve developed a higher-order function named withSetup
. This utility allows us to create a Vue component context programmatically, focusing primarily on the setup lifecycle function where composables are typically used.
Introduction to withSetup
withSetup
is designed to simulate a Vue component’s setup function, enabling us to test composables in an environment that closely mimics their real-world use. The function accepts a composable and returns both the composable’s result and a Vue app instance. This setup allows for comprehensive testing, including lifecycle and reactivity features.
import type { interface App<HostElement = any>
App } from "vue";
import { const createApp: CreateAppFunction<Element>
createApp } from "vue";
export function function withSetup<T>(composable: () => T): [T, App]
withSetup<function (type parameter) T in withSetup<T>(composable: () => T): [T, App]
T>(composable: () => T
composable: () => function (type parameter) T in withSetup<T>(composable: () => T): [T, App]
T): [function (type parameter) T in withSetup<T>(composable: () => T): [T, App]
T, interface App<HostElement = any>
App] {
let let result: T
result: function (type parameter) T in withSetup<T>(composable: () => T): [T, App]
T;
const const app: App<Element>
app = function createApp(rootComponent: Component, rootProps?: Data | null): App<Element>
createApp({
ComponentOptionsBase<any, any, any, ComputedOptions, MethodOptions, any, any, any, string, {}, {}, string, {}, {}, {}, string, ComponentProvideOptions>.setup?: ((this: void, props: LooseRequired<any>, ctx: {
attrs: Data;
slots: Readonly<InternalSlots>;
emit: ((event: unknown, ...args: any[]) => void) | ((event: string, ...args: any[]) => void);
expose: <Exposed extends Record<string, any> = Record<string, any>>(exposed?: Exposed) => void;
}) => any) | undefined
setup() {
let result: T
result = composable: () => T
composable();
return () => {};
},
});
const app: App<Element>
app.App<Element>.mount(rootContainer: string | Element, isHydrate?: boolean, namespace?: boolean | ElementNamespace, vnode?: VNode): ComponentPublicInstance
mount(var document: Document
[MDN Reference](https://developer.mozilla.org/docs/Web/API/Window/document)document.Document.createElement<"div">(tagName: "div", options?: ElementCreationOptions): HTMLDivElement (+2 overloads)
Creates an instance of the element for the specified tag.createElement("div"));
return [let result: T
result, const app: App<Element>
app];
}
In this implementation, withSetup
mounts a minimal Vue app and executes the provided composable function during the setup phase. This approach allows us to capture and return the composable’s output alongside the app instance for further testing.
Utilizing withSetup
in Tests
With withSetup
, we can enhance our testing strategy for composables like useLocalStorage
, ensuring they behave as expected even when they depend on lifecycle hooks:
it("should load the value from localStorage if it was set before", async () => {
var localStorage: Storage
[MDN Reference](https://developer.mozilla.org/docs/Web/API/Window/localStorage)
A browser-compatible implementation of [`localStorage`](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage).
Data is stored unencrypted in the file specified by the `--localstorage-file` CLI flag.
Any modification of this data outside of the Web Storage API is not supported.
Enable this API with the `--experimental-webstorage` CLI flag.localStorage.Storage.setItem(key: string, value: string): void
Sets the value of the pair identified by key to value, creating a new key/value pair if none existed for key previously.
Throws a "QuotaExceededError" DOMException exception if the new value couldn't be set. (Setting could fail if, e.g., the user has disabled storage for the site, or if the quota has been exceeded.)
Dispatches a storage event on Window objects holding an equivalent Storage object.
[MDN Reference](https://developer.mozilla.org/docs/Web/API/Storage/setItem)setItem("testKey", var JSON: JSON
An intrinsic object that provides functions to convert JavaScript values to and from the JavaScript Object Notation (JSON) format.JSON.JSON.stringify(value: any, replacer?: (this: any, key: string, value: any) => any, space?: string | number): string (+1 overload)
Converts a JavaScript value to a JavaScript Object Notation (JSON) string.stringify("valueFromLocalStorage"));
const [const result: {
value: Ref<string, string>;
}
result] = function withSetup<{
value: Ref<string, string>;
}>(composable: () => {
value: Ref<string, string>;
}): [{
value: Ref<string, string>;
}, App<any>]
withSetup(() => function useLocalStorage<string>(key: string, initialValue: string): {
value: Ref<string, string>;
}
useLocalStorage("testKey", "testValue"));
expect(const result: {
value: Ref<string, string>;
}
result.value: Ref<string, string>
value.Ref<string, string>.value: string
value).toBe("valueFromLocalStorage");
});
This test demonstrates how withSetup
enables the composable to execute as if it were part of a regular Vue component, ensuring the onMounted
lifecycle hook is triggered as expected. Additionally, the robust TypeScript support enhances the development experience by providing clear type inference and error checking.
Summary
In our exploration of testing Vue composables, we uncovered two distinct categories: Independent Composables and Dependent Composables. Independent Composables stand alone and can be tested akin to regular functions, showcasing straightforward testing procedures. Meanwhile, Dependent Composables, intricately tied to Vue’s component system and lifecycle hooks, require a more nuanced approach. For these, we learned the effectiveness of utilizing a helper function, such as withSetup
, to simulate a component context, enabling comprehensive testing.
I hope this blog post has been insightful and useful in enhancing your understanding of testing Vue composables. I’m also keen to learn about your experiences and methods in testing composables within your projects. Your insights and approaches could provide valuable perspectives and contribute to the broader Vue community’s knowledge.