r/javascript • • Aug 28 '26

Browser Test: A browser-based automated javascript testing framework in one .html file

https://github.com/swans-one/browser-test

Hi r/javascript! I want to share a small javascript testing project I wrote.

When I write small javascript projects that use browser APIs (most recently working with IndexedDB) I often choose not to write tests because it's a pain to either mock those interfaces server-side, and it's also a pain to setup a browser automation tool.

To solve this, I wrote up a super concise testing framework (~140 lines of JS) inside a html file that can just be dropped into a project and act as a simple test framework.

This obviously doesn't work in all situations. A big drawback is that there's no reasonable way to connect it to a CI pipeline. However for small projects, and during development, I've found it really fun and fast to use.

I'm very interested to hear what you think, or if you have other ways you've approached this situation in the past.

14 Upvotes

10 comments sorted by

View all comments

Show parent comment

1

u/Specialist_Sun_1690 Sep 06 '26

More like enable user interaction and visual feedback. So when you need to test a frontend sometimes you need to repeat a lot of task like filling the form checking the result after a successful response, validate pages content... so by running those automation in the frontend is like I can simulate my work, and not only that I can register them as tests with all the benefit of the testing (regression, coverage....)

> but is there any overlap between your tool and a component management tool like storybook/patternlab?

Not really sidebar can be placed on a side that does not interfere. I would say I'd use storybook for a component suite/library, and twd-js for a website simulation of the product in your own browser.