assaf/zombieArchived
Zombie
Zombie is a headless browser testing framework and full-stack test runner that simulates a complete browser environment entirely within Node.js. It renders and manipulates a virtual DOM using JavaScript alone, without relying on any native browser engine, and processes events, scripts, and page interactions through a single-threaded event loop. This makes it a Node.js browser automation tool that can load, navigate, and interact with web pages programmatically for testing, scraping, or debugging purposes.
The framework distinguishes itself through several integrated capabilities that work together in a single process. It provides a CSS selector-based assertion engine for checking page content and state, with support for regex patterns and custom error messages. Zombie manages browser sessions through cookie-based state tracking with domain and path specificity, and supports multiple tabs or windows as isolated contexts that can be opened, closed, and switched by index or name. It also includes a request-response interception pipeline that can intercept and modify HTTP, HTTPS, and file resources, along with hostname-to-server routing that maps named domains and ports to local test servers for realistic testing without network access.
The tool covers the full lifecycle of browser-based testing, including form interaction, page state assertion, and cookie management. It can fill out and submit web forms, select options, check boxes, and trigger page transitions during tests. Zombie also supports extension-based customization, allowing every new browser instance to be modified with additional properties, listeners, or methods through an extension function.
Features
- Headless Browser Testing Frameworks - Runs automated browser tests from the command line without a visible UI, simulating page loads, clicks, and form submissions in Node.js.
- Simulated Browser Environments - Simulates a full browser environment by processing events, scripts, and page interactions in a single-threaded Node.js event loop.
- Cookie-Based Session Management - Manages browser sessions by storing and matching cookies with domain and path specificity for each page context.
- Assertion Engines - Provides a CSS selector-based assertion engine for checking page content and state with regex and custom error messages.
- Page State Assertions - Checks page content, element attributes, styles, URLs, cookies, and status codes using CSS selectors and built-in assertion methods.
- Form Interaction Utilities - Fills out and submits web forms programmatically, selecting options, checking boxes, and triggering page transitions during tests.
- Browser Automation Tools - Loads, navigates, and interacts with web pages entirely within Node.js using a JavaScript-based browser engine.
- Full-Stack Test Runners - Executes client-side scripts, processes DOM events, and manages server-side state from a single Node.js process.
- DOM Implementations - Renders and manipulates a virtual DOM entirely in JavaScript without relying on a native browser engine.
- Request Interception - Intercepts HTTP, HTTPS, and file resources by passing them through a configurable pipeline of request and response handlers.
- HTTP Request Interceptors - Intercepts and modifies HTTP, HTTPS, or file resources through request and response handler pipelines during browser tests.
- Multi-Tab Simulators - Opens, closes, and switches between multiple browser windows or tabs by index or name to test tab-dependent workflows.
- Tab-Based Window Managers - Supports multiple browser tabs or windows as isolated contexts that can be opened, closed, and switched by index or name.
- Testing Utilities - Sets, retrieves, and deletes cookies with domain and path specificity to test cookie-dependent application behavior.
- Test Runners - Fast, full-stack headless browser for Node.js.
- Testing Frameworks - Insanely fast, full-stack, headless browser testing using node.js.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
