Advertisement · 728 × 90

Posts by QUnit

Two rolls of QUnit stickers, as well as various jQuery "Keep calm and call on()" stickers, Wikipedia stickers, and MediaWiki logo stickers.

Two rolls of QUnit stickers, as well as various jQuery "Keep calm and call on()" stickers, Wikipedia stickers, and MediaWiki logo stickers.

Stickers packed and ready for FOSDEM!

Message me to meet and take some!

#fosdem #fosdem2026 #qunit #jquery

2 months ago 3 0 0 0
QUnit 2.25.0 Released: Add callback filter Introduce QUnit.config.testFilter to programmatically filter tests.

QUnit 2.25 is out!

Highlights from 2.24.1 and 2.25.0:

🧩 Support display of "early" errors in the HTML Reporter.
✨ New test filter callback, for parallel test runners and other cool stuff. Thanks Sebastian Gbudje and @nullvoxpopuli.com!
🐛 Fix bugs in the TAP-reporter.

qunitjs.com/blog/2025/12...

3 months ago 3 1 0 0
Post image

Did you know you can using @testing-library/dom with zero configuration in ember projects?

4 months ago 2 1 2 0

👤 Post by ansgarl (by SAP):
"How to use latest QUnit and sinon to test your SAPUI5 applications"
🔗 Link: community.sap.com/t5/technology-blog-posts...

7 months ago 3 1 1 0
Preview
GitHub - qunitjs/qtap: Run JavaScript unit tests in real browsers, real fast. Run JavaScript unit tests in real browsers, real fast. - qunitjs/qtap

@nullvoxpopuli.com @erus.dev

That's essentially the idea behind QTap.

github.com/qunitjs/qtap

Airtap and karma-tap came close but neither support HTML, and Airtap also imposes bundling, so you end up coupled to the runner incl debugging.

Watch this space.
Early feedback welcome!

9 months ago 3 2 0 0

(How I use) Qunit:
- testem for cli reporter (not qunit)
- (bulilt assets to load (I'd prefer vite's way)
- testem for launching pre-installed browsers (doesn't force installation via npm like like puppeteer does, iirc)
- qunit for test runner
- qunit for test framework

9 months ago 0 1 1 0
Imagine a test with global hooks, and a Parent and Child module that use hooks also. The execution order is:
1. Parent module runs the before hook.
2. Every test in the Parent module inherits context from the before hook, and repeats as follows: call global beforeEach, parent beforeEach, the actual test, parent afterEach, and lastly the global afterEach.
3. The Child module inherits context from the Parent before hook, and then runs its own before hook.
4. Every test in the Child module inherits context from this before hook, and repeats as follows: call global beforeEach, parent beforeEach, child beforeEach, the actual test, child afterEach, parent afterEach, and lastly the global afterEach.

Imagine a test with global hooks, and a Parent and Child module that use hooks also. The execution order is: 1. Parent module runs the before hook. 2. Every test in the Parent module inherits context from the before hook, and repeats as follows: call global beforeEach, parent beforeEach, the actual test, parent afterEach, and lastly the global afterEach. 3. The Child module inherits context from the Parent before hook, and then runs its own before hook. 4. Every test in the Child module inherits context from this before hook, and repeats as follows: call global beforeEach, parent beforeEach, child beforeEach, the actual test, child afterEach, parent afterEach, and lastly the global afterEach.

Ever wondered how beforeEach works in a unit test framework?

qunitjs.com/lifecycle/

While people generally guess right, this demonstrates that the order is guaranteed, and showcases what's possible when you depend on it.

Thanks to FND, Jan D, and NullVoxPopuli for their help!

#qunit

11 months ago 2 1 0 0
WebdriverIO QUnit Service testing results for a UI5 app.

WebdriverIO QUnit Service testing results for a UI5 app.

WebdriverIO QUnit Service now supports all sort of QUnit usage in SAP Fiori and UI5 apps! Whatever UI5/QUnit testing method you're using, you can run it with wdio-qunit-service.
All you need is a wdio.conf.js file. Have a look at an example:
github.com/SAP/openui5-...

1 year ago 2 1 2 0
Original post on mastodon.social

My final post for the year on @TheNewStack is a wrapup of the leading #webdev trends of 2024:

“The year in web development was characterized by a return to simpler ways of building a website or web application. Partly this was a reaction against the increasing complexity of JavaScript […]

1 year ago 1 4 0 0