Analysis updated 2026-05-18
Automatically test a web app for rule violations by driving a real Chrome browser against it in CI.
Test a command line program's output against defined rules using the terminal driver.
Catch bugs before merge by running property based tests on every pull request.
Save traces and screenshots as build artifacts to inspect failures after a CI run.
| antithesishq/bombadil-action | 0xradioac7iv/tempfs | abboskhonov/hermium | |
|---|---|---|---|
| Stars | 0 | 0 | 0 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 3/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires writing a specification file and configuring a running app or command to test against.
bombadil-action is a GitHub Action that runs Bombadil property based tests as part of a continuous integration workflow. Bombadil itself is a separate tool that checks whether an application behaves correctly by exploring it and looking for violations of rules you define, and this action wires that tool into a GitHub Actions job so it runs automatically on every push or pull request. The action supports two drivers. The browser driver, which is the default, opens a real Chrome browser and points it at a URL you provide, then tests the running application against a specification file you write in TypeScript or JavaScript. The terminal driver instead runs a command line program and checks its text output against the same kind of specification. You choose which driver to use with a simple input setting. For the browser driver, you set an origin URL, a specification file path, and a time limit so the test does not run forever. You can also pass custom HTTP headers, such as an authorization token, and adjust settings like viewport size. The action installs Chrome for Testing automatically and caches the download so later runs are faster. If your workflow already has Chrome installed, you can point the action at it instead and skip the download. The terminal driver needs a command to run, how many test cases to generate, and an optional random seed so results can be repeated later. After a run, the action reports an exit code showing whether everything passed, a rule was violated, or something else went wrong. You can save the output as a build artifact and inspect it afterward to see exactly what happened during testing. The README shows examples for testing a locally started server and for testing an application running in Docker containers, including how to wait for the app to be ready before the test begins. The full README is longer than what was shown.
A GitHub Action that runs Bombadil property based tests, against either a live browser session or a command line program's output, inside a CI workflow.
Mainly TypeScript. The stack also includes TypeScript, GitHub Actions, Chrome.
No license information is stated in the README.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.