Community packages

Find third-party packages that extend e2e and submit an integration.

Community packages extend e2e with tools, engines, and reporters. Their maintainers, not the e2e core team, maintain and support them. A listing is not an endorsement.

Check each package’s documentation for supported e2e versions and setup requirements. The versions below record published packages checked on November 12, 2026, not compatibility tests by the e2e team.

Find a package

e2e-cige

Runs CIGE test cases as JSON through agent.act and agent.assert. Includes run summaries and checks for agents that repair failing tests.

Maintainer: Vivek Krishna. Version 0.1.0 declares e2e >=0.21.0 <1.

npm · Repository and setup

@appduct/e2e

Calls an app’s Appduct tools from test fixtures or agent steps over MCP. Supports web, iOS simulator, and Android emulator targets.

Maintainer: Callstack. Version 0.16.0 declares e2e >=0.21.0 <1 and ai ^7.0.0.

npm · Repository and setup

@mobai-app/e2e

Adds a MobAI device engine and dashboard reporter for physical iOS and Android devices, simulators, emulators, and device farms.

Maintainer: MobAI. Version 0.1.3 declares e2e >=0.19.0 <1.

npm · Repository and setup

@testdino/e2e

Reports test cases, retries, steps, errors, console output, screenshots, and videos to TestDino.

Maintainer: TestDino. Version 1.1.0 declares e2e >=0.16.0 <1. Selection and rerun commands require e2e 0.19.0 or later.

npm · Documentation

@testomatio/reporter

Sends e2e results to Testomat.io through its @testomatio/reporter/e2e adapter.

Maintainer: Testomat.io. Version 2.23.0 includes the adapter. Its example uses e2e ^0.21.0; the package declares no e2e peer range.

npm · Repository and example

The e2e team maintains the hosted browser and device integrations, GitHub reporter, and built-in reporters.

For application suites and provider examples, browse community and partner examples. These include Limrun’s app-flow example and Notte’s browser provider example.

Add yours

Open a pull request to edit this page. Include:

The package name, a published package link, and its repository or documentation.
A short description of how it integrates with e2e, with a source or usage example.
The maintainer, supported platforms, and e2e compatibility requirements.
The version and publication date checked for the addition.

Keep the description factual. Report package issues to its maintainer. Submit application examples through the examples contribution guide.