Exploration-side companion
Tabula QA is built for discovery before runtime automation begins, especially on pages that need login, setup, or manual navigation.
Browser-Assisted Page Mapping
Map what matters before you automate.
Tabula QA is a browser-assisted page discovery and mapping tool for automated QA workflows. It helps teams capture meaningful DOM structure, export actionable JSON, and explore pages without forcing that responsibility into the test runtime.
Open a real browser and capture the page state that matters
Support assisted flows where humans prepare the target screen
Export structured JSON for downstream automation workflows
What It Is
Discovery and mapping before runtime automation begins.
Tabula QA is the exploration-side companion to runtime diagnosis tools like Revelium. Its job is to open a real browser, capture the current page state, discover useful DOM structure, and export a map teams can inspect or reuse downstream.
Mapping over guessing
Instead of forcing page discovery into test execution, it captures the current DOM and produces locator-oriented structure teams can inspect and reuse.
Human-assisted when needed
Assisted mode is part of the product design, not a fallback. It is useful when the important page state depends on real user preparation.
How Assisted Capture Works
Pause when a human is useful, export when the page is ready.
- 1
Open a Selenium browser session and navigate to the target URL
- 2
Optionally pause in assisted mode so a human can prepare the page
- 3
Capture the current page source and build a structured page map
- 4
Export JSON with elements, categories, suggested names, and inferred locators
Useful when page state depends on
authenticationconsent bannersmenus and drawersmulti-step flows
Assisted capture is valuable exactly because many relevant QA states do not exist at the first page load.
Quick Start
Terminal-first commands for capture and inspection.
pip install tabula-qa
tabula-qa capture "https://example.com" --assisted --output tabula_reports/page_map.json
tabula-qa inspect tabula_reports/page_map.json- mapping screens before automation work starts
- exploring complex states after login or setup
- exporting locator-oriented JSON for downstream tooling
- documenting what a page currently exposes to QA
Output
Locator-oriented JSON designed for QA workflows.
page URLpage titlediscovered elementssuggested namesbutton, field, form, link, and table categorieslocators inferred from data-testid, id, name, and aria-label
The current scope is intentionally focused on browser-assisted capture, page discovery, structured page maps, and terminal inspection of saved output.
Current Status
Early product foundation, already usable.
Tabula QA is still in an early alpha stage, but it is already useful for DOM discovery and assisted capture. Export and inspection workflows should still be treated as evolving.
v0.1.0 alpha
View repository on GitHubRelationship
Exploration here, runtime diagnosis in Revelium.
The split is intentional: Tabula QA owns exploration and mapping workflows, while Revelium stays focused on runtime failure diagnosis. Together they cover discovery before automation and diagnosis after breakage.
View ReveliumPositioning
Built for teams that want cleaner page understanding before writing automation.
Tabula QA fits QA, SDET, and platform teams that need a faster path to inspect screens, document exposed structure, and export reusable page maps from real browser states.
Interested in Tabula QA? Want to shape the workflow around your team?