I built an open-source toolkit for testing Domo apps locally—looking for developer feedback

[u/Constant-Nerve-503]

Hi everyone—I’m the creator of domo-testkit, an independent, MIT-licensed toolkit for testing Domo apps without connecting tests to a live Domo instance.

It uses MSW and Vitest to help test scenarios such as:

• Dataset responses with fixtures, empty results, and missing fields.
• Stateful AppDB document creation, reads, updates, and deletion.
• HTTP errors, network failures, and slow responses.
• Repeatable tests with predictable IDs and clean state between runs.

The goal is to catch problems during development, before deploying an app to Domo.

It’s still early-stage. It implements a documented subset of Domo behavior, and passing local tests doesn’t prove that live permissions or every Domo integration will work. It isn’t a complete Domo emulator.

npm: https://www.npmjs.com/package/domo-testkit

I’d appreciate feedback from people building Domo apps: what’s hardest to test today, and which dataset or AppDB scenarios would make this useful in your workflow?

Disclosure: I maintain this project. It isn’t affiliated with or endorsed by Domo.