Dommy

A pure-Ruby, browser-like DOM stack for testing Rack/Rails apps without a real browser. This repository is a monorepo containing the core library and its integration gems.

Gems

Gem	Path	Description
`dommy`	`gems/dommy`	happy-dom-style DOM polyfill in pure Ruby (Makiri backend).
`dommy-rack`	`gems/dommy-rack`	Rack-backed, browser-like session layer over a `Dommy::Document`.
`capybara-dommy`	`gems/capybara-dommy`	A Capybara driver backed by `dommy` and `dommy-rack`.
`dommy-rails`	`gems/dommy-rails`	Rails-specific DOM matchers and assertions for request/view/component/mailer specs.

Each gem keeps its own gemspec, README, and test suite, and is released to RubyGems independently.

Note

dommy-js-quickjs (a QuickJS JavaScript backend) lives in its own repository because it depends on the native quickjs gem with a separate build/release cadence.

Development

A single root Gemfile resolves all gems from their local paths, so no path: overrides are needed:

bundle install

Running tests

# Every gem
bundle exec rake test

# A single gem
bundle exec rake test:dommy
bundle exec rake test:dommy-rack
bundle exec rake test:capybara-dommy
bundle exec rake test:dommy-rails

You can also run a gem's suite from its own directory:

cd gems/dommy && bundle exec rake

dommy, dommy-rack, and dommy-rails use Minitest; capybara-dommy uses RSpec (including the Capybara driver compliance suite).

Internal method naming (`xxx`)

Methods wrapped in double underscores are not part of the public DOM API — the name marks them as internal or bridge-only. To keep them from proliferating ad-hoc, every such method must use exactly one of these four prefixes:

Prefix	Purpose
`__js_*__`	Bridge protocol for external JS runtimes (`__js_get__` / `__js_set__` / `__js_call__` / `__js_new__`, …). The contract lives in `lib/dommy/bridge.rb`.
`__internal_*__`	Spec-internal steps and non-public cross-object coordination (the largest group).
`__test_*__`	Test-only hooks for simulating events the environment would otherwise raise (`__test_trigger__`, …).
`__dommy_*__`	Backend (makiri) integration (`__dommy_backend_node__`, `__dommy_bytes__`).

When adding an internal coordination method, prefix it with __internal_. Do not introduce new bare __name__ methods outside these four families.

Releasing

Build and push each gem from its own subdirectory:

cd gems/dommy && bundle exec rake release

License

MIT — see LICENSE.txt.

dommy-rack

Runtime