Testing overview

Every helper in this library reads its data through the CONVEX injection token. The convex-angular/testing entry point exists so a test can put something else behind that token: an in-memory MockConvexClient that captures every subscription and invocation the helpers make, and hands the test the controls to drive them.

That means no deployment, no WebSocket, and no network. A query does not resolve until your test emits a value; a mutation’s promise does not settle until your test settles it. Timing is entirely yours, so loading states, error states, and out-of-order responses are all reachable deterministically.

import { MockConvexClient, provideConvexTesting } from 'convex-angular/testing';

The entry point exports exactly two runtime values — MockConvexClient and provideConvexTesting — plus the seven types describing what it captures. See Mock reference for the full API and Driving state for the how-to matrix.

Setting up a TestBed

provideConvexTesting(client) returns providers registering your mock under the CONVEX token. Drop it into TestBed.configureTestingModule. You do not call provideConvex() in tests — the testing provider replaces it.

import { TestBed } from '@angular/core/testing';
import { MockConvexClient, provideConvexTesting } from 'convex-angular/testing';

let convex: MockConvexClient;

beforeEach(() => {
  convex = new MockConvexClient();
  TestBed.configureTestingModule({
    providers: [provideConvexTesting(convex)],
  });
});

afterEach(() => {
  TestBed.resetTestingModule();
});

Keep the mock in a variable. The argument is optional — provideConvexTesting() creates a fresh mock — but then the test has no handle to drive it with.

Caution

MockConvexClient has no reset method. Its capture arrays (querySubscriptions, paginatedSubscriptions, mutationCalls, actionCalls, authRegistrations, localQueryResultCalls, refusedSubscriptions) are never cleared, and neither are its counters (clearAuthCount, hasAuthCount, the connection-state counts). Construct a new MockConvexClient in beforeEach so index-based assertions such as convex.mutationCalls[0] refer to the current test’s call and not a leftover from the previous one.

Components that use auth

provideConvexTesting() registers the CONVEX token and nothing more, so injectAuth(), the auth directives, and the route guards still need their own registration in the test: a ConvexAuthProvider behind CONVEX_AUTH, plus provideConvexAuth().

TestBed.configureTestingModule({
  providers: [provideConvexTesting(convex), { provide: CONVEX_AUTH, useValue: fakeAuthProvider }, provideConvexAuth()],
});

That pairing is what makes the mock’s auth surface interesting: your fake provider plays the identity system, and convex.lastAuthRegistration() plays Convex answering back. See Authentication.

A complete component test

Take an ordinary standalone component that reads a live query and runs a mutation:

todo-list.ts

import { Component } from '@angular/core';
import { injectMutation, injectQuery } from 'convex-angular';

import { api } from '../convex/_generated/api';

@Component({
  selector: 'app-todo-list',
  template: `
    @switch (todos.status()) {
      @case ('pending') {
        <p>Loading…</p>
      }
      @case ('error') {
        <p role="alert">{{ todos.error()?.message }}</p>
      }
      @case ('success') {
        <ul>
          @for (todo of todos.data(); track todo._id) {
            <li>{{ todo.title }}</li>
          }
        </ul>
      }
    }

    <button type="button" [disabled]="addTodo.isLoading()" (click)="add()">Add</button>
  `,
})
export class TodoList {
  readonly todos = injectQuery(api.todos.list, () => ({}));
  readonly addTodo = injectMutation(api.todos.create);

  add(): void {
    void this.addTodo.mutate({ title: 'New todo' });
  }
}

The test drives both sides of it:

todo-list.spec.ts

import { TestBed, fakeAsync, tick } from '@angular/core/testing';
import { MockConvexClient, provideConvexTesting } from 'convex-angular/testing';

import { TodoList } from './todo-list';

describe('TodoList', () => {
  let convex: MockConvexClient;

  beforeEach(() => {
    convex = new MockConvexClient();
    TestBed.configureTestingModule({
      imports: [TodoList],
      providers: [provideConvexTesting(convex)],
    });
  });

  afterEach(() => {
    TestBed.resetTestingModule();
  });

  it('renders the todos pushed by the subscription', fakeAsync(() => {
    const fixture = TestBed.createComponent(TodoList);
    fixture.detectChanges();
    tick();

    // The subscription exists, with the args the component built.
    expect(convex.querySubscriptions).toHaveLength(1);
    expect(convex.lastQuerySubscription()!.args).toEqual({});
    expect(fixture.componentInstance.todos.status()).toBe('pending');

    convex.lastQuerySubscription()!.emit([{ _id: '1', title: 'Write docs' }]);
    fixture.detectChanges();

    expect(fixture.componentInstance.todos.status()).toBe('success');
    expect(fixture.nativeElement.textContent).toContain('Write docs');
  }));

  it('keeps the button disabled until the mutation settles', fakeAsync(() => {
    const fixture = TestBed.createComponent(TodoList);
    fixture.detectChanges();
    tick();

    fixture.componentInstance.add();
    tick();
    fixture.detectChanges();

    expect(convex.mutationCalls).toHaveLength(1);
    expect(convex.mutationCalls[0].args).toEqual({ title: 'New todo' });
    expect(fixture.componentInstance.addTodo.status()).toBe('pending');

    convex.mutationCalls[0].resolve('todo-id');
    tick();
    fixture.detectChanges();

    expect(fixture.componentInstance.addTodo.status()).toBe('success');
    expect(fixture.componentInstance.addTodo.data()).toBe('todo-id');
  }));

  it('unsubscribes when the fixture is destroyed', fakeAsync(() => {
    const fixture = TestBed.createComponent(TodoList);
    fixture.detectChanges();
    tick();

    fixture.destroy();

    expect(convex.lastQuerySubscription()!.unsubscribed).toBe(true);
  }));
});

The library’s own tests use Jest with jest-preset-angular and a zone-based TestBed. Nothing in the mock depends on that choice — it is a plain object graph — but the change-detection rhythm below assumes a zone-based fixture.

The rhythm: subscribe, emit, detect

Query helpers do not subscribe when they are injected. injectQuery(), injectQueries(), and injectPaginatedQuery() each open their subscription inside an effect(), and effects do not run until change detection runs. This has one concrete consequence for tests:

const fixture = TestBed.createComponent(TodoList);

// Nothing has subscribed yet — the effect has not run.
expect(convex.querySubscriptions).toHaveLength(0);

fixture.detectChanges();

// Now the subscription exists and can be driven.
expect(convex.querySubscriptions).toHaveLength(1);

The same applies after any change to a signal the argument function reads. Setting the signal marks the effect dirty; it does not run it. Run change detection again, and the effect re-subscribes:

fixture.componentInstance.category.set('work');
fixture.detectChanges();
tick();

// A second subscription was captured; the first was unsubscribed.
expect(convex.querySubscriptions).toHaveLength(2);
expect(convex.querySubscriptions[0].unsubscribed).toBe(true);
expect(convex.lastQuerySubscription()!.args).toEqual({ category: 'work' });

Inside fakeAsync, follow detectChanges() with tick() to flush the microtasks the helpers schedule. Emissions themselves are synchronous: emit() calls the helper’s callback directly, so the signals update on the spot and can be asserted without another tick(). Change detection is still needed before asserting rendered DOM.

Tip

A short checklist for any Convex-backed component test:

1. Fresh MockConvexClient in beforeEach.
2. createComponent then detectChanges() (and tick() under fakeAsync) — this is what subscribes.
3. Assert the captured subscription’s args, so a wrong argument fails loudly instead of silently querying nothing.
4. emit() / resolve() to drive, then detectChanges() before asserting the DOM.
5. detectChanges() again after every signal change that feeds an argument function.

Next

Driving state is the practical matrix: results, errors, pages, mutation settlement, authentication, warm-cache prefill, connection state, and the disabled (SSR) mock.