QUnit Test Best Practices for UI5

When to load each reference

Trigger	Load
Writing a new QUnit test file or module from scratch	`references/writing-new-tests.md`
Modernizing, refactoring, or reviewing existing test code	`references/modernizing-tests.md`
Migrating from QUnit 1 (globals: `test`, `asyncTest`, `ok`, `stop`, `start`) to QUnit 2	`references/modernizing-tests.md`
Any test touches `nextUIUpdate`, `Core.applyChanges`, `assert.async`, fake timers, or event-based async	`references/async-patterns.md`

Load the reference before producing any output. Do not work from memory.

Installs

Repository

GitHub Stars

First Seen

14 days ago

Security Audits